Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 367303

Summary: Implement "Locate Value" Action in Properties View
Product: [Modeling] MDT.RMF Reporter: Michael Jastram <michael>
Component: ProRAssignee: Hussein MHANNA <hussein.mhanna>
Status: ASSIGNED --- QA Contact:
Severity: enhancement    
Priority: P3 CC: eclipse, lukas.ladenberger
Version: unspecified   
Target Milestone: 0.14.0   
Hardware: All   
OS: All   
Whiteboard:

Description Michael Jastram CLA 2011-12-21 06:37:01 EST 
Implement "Locate Value" Action in Properties View. The problem is that the current viewer in the UIEditor class is null. We have to set the current viewer to the ProR agile grid viewer.

Migrated from http://dev.pror.org/ticket/47
Comment 1 Hussein MHANNA CLA 2015-06-05 17:08:08 EDT 
Michael,

Could you please describe what the locate value must select in the Editor?

We cannot select attribute values because the displayed objects in the editor are the SpecHierarchy's.
Comment 2 Michael Jastram CLA 2015-06-09 12:45:36 EDT 
> Could you please describe what the locate value must select in the Editor?

> We cannot select attribute values because the displayed objects in the editor are the SpecHierarchy's.

Yes, because the editor contains SpecHierarchies, that's what we need to select.  So we have to find the SpecHierarchy that corresponds to the given AV.

In theory, we just have to find the corresponding parent object, but this could indeed be tricky.

First, it should be easy to find the SpecObject that the AV belongs to (by using eParent().

If the Property View's content is based on a SpecObject, then we are out of luck.  Unless we want to inspect the Editor's Specification and find ALL SpecHierarchies that reference that SpecObject.

However, the PropertyView's content may be based on a SpecHierarchy, and then you are pretty much done.
Comment 3 Mark Broerkens CLA 2015-08-11 04:09:36 EDT 
moved to 0.14.0