| Summary: | Expression Label Mappings for Connections do not work | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] GMF-Tooling | Reporter: | Ralph Gerbig <ralphgerbig> | ||||
| Component: | Core | Assignee: | Project Inbox <gmp.gmf-tooling-inbox> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | borlander | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ralph Gerbig
The connection that contains the expression label has only the target feature set. Maybe this is why the bug is happening in may case. Created attachment 199256 [details]
Patch that places the VisualId of the edit part behind the parser
Could not test it as I always get a out of memory exception when trying to generate a generator model in my target workspace. Maybe someone els can test it.
The idea is to put the VisualID of the LabelEditPart that uses it behind its class name. This way more than one expression labels can be created for the same mapping.
Wrong Patch. The Patch was intended for Bug 331875... (In reply to comment #2) > Created attachment 199256 [details] > Patch that places the VisualId of the edit part behind the parser > Could not test it as I always get a out of memory exception when trying to > generate a generator model in my target workspace. Maybe someone els can test > it. > The idea is to put the VisualID of the LabelEditPart that uses it behind its > class name. This way more than one expression labels can be created for the > same mapping. severity reduced, not critical -- user always can use the custom parser as a workaround. |