| Summary: | NPE on adding a new element to a compartment with label figures and list layout | ||
|---|---|---|---|
| Product: | [Modeling] GMF-Tooling | Reporter: | Steffen Becker <steffen.becker> |
| Component: | Core | Assignee: | Artem Tikhomirov <tikhomirov.artem> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | 2.0 | ||
| Hardware: | PC | ||
| OS: | Windows NT | ||
| Whiteboard: | |||
|
Description
Steffen Becker
Looks like there's smth wrong with gmfgraph model. You were right, good guess :-) The issue was that the label which should get displayed in the compartment was defined as child of a Rectangle in GMFGraph, something which seemed to be legacy from migrating the models for 1,5 year now. Obviously GMF2 M7 and earlier had no problem with this, but RC2 now has. I consider the GMFGraph as it was before as invalid, right? I would suggest, there should be a constraint that checks that labels which are used in compartments directly are the only child of a figure description - or something similar. (In reply to comment #2) Labels inside compartment are full-fledged nodes, just represented with a simple line of text. Nested figures (e.g. child label inside a rectangle) are not for such usecases, they should be used to denote e.g. predefined position of label or to ensure its instantiation at apropriate moment of time. IOW, figure inside figure represents exact instance, while DiagramElement (and the figure it links) represents *class* of instances, hence, using child figures for this is not appropriate. [target cleanup] 2.0 RC was the original target milestone for this bug [GMF Restructure] Bug 319140 : product GMF and component Generation was the original product and component for this bug |