| Summary: | Provide user selection context in IDirectEditing APIs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Graphiti | Reporter: | Nurali <nurali_virani> | ||||
| Component: | Core | Assignee: | Project Inbox <graphiti-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | dhawal.joshi, matthias.gorning, michael.wenz, nurali_virani | ||||
| Version: | 0.7.0 | Flags: | michael.wenz:
indigo+
|
||||
| Target Milestone: | 0.8.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | Indigo M7 theme_round_offs | ||||||
| Attachments: |
|
||||||
|
Description
Nurali
The same issue appears in the stantard EClass diagram editor when you have several ECLass objects with the same name belonging to different EPackages. A workaround is already possible today: the names provided by getValueProposal must contain additional information that is suitable to identify the selected object (in the above example this would be something like <class name> - <package name>). Created attachment 178407 [details]
Details for workaround
The attached file contains details on the described workaround for a similiar problem in a MOF Class Editor
Done. There is a new method in IDirectEditing: IProposalSupport getProposalSupport(); Done. There is a new method in IDirectEditing which can be implemented to achieve the proposed behavior: IProposalSupport getProposalSupport(); An example can be found in the class SketchTextProposalDirectEditingFeature. Part of 0.8.0 Part of Graphiti Indigo 0.8.0 |