Summary: | Refresh is not automatically launched after a compartment specification update | ||||||
---|---|---|---|---|---|---|---|
Product: | [Modeling] Sirius | Reporter: | Etienne Juliot <etienne.juliot> | ||||
Component: | Diagram | Assignee: | Project Inbox <sirius.diagram-inbox> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | esteban.dugueperoux, maxime.porhel | ||||
Version: | 3.1.0 | Keywords: | triaged | ||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows NT | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Etienne Juliot
2015-12-23 09:36:09 EST
Created attachment 258924 [details]
Example to reproduce
I don't reproduce your refresh issue with the attached sample, could you test with it and update it to be able to have a reproduction scenario?
I downloaded your attachment and I can easily reproduce the bug: just modify the Domain class of ChildrenMapping from basicfamily.Person to basicfamily.Woman. When you will save the .odesign file, nothing appears: you need to manually call the refresh. I tested this scenario with freeform and list styles: it occurs only with compartments. Steps to reproduce: . Unzip the provided reproduction case and launch a runtime. . Create a basic family model, populate it with a Man A father of Man B father and a Man C, . Create a session, activate the provided Persons viewpoint and create a diagram . Open the family tree editor and place the diagram and the editor side by side . In the tree editor, set B as father of Man C . C should appear as a sub node of B in the diagram. (In reply to Maxime Porhel from comment #4) > Steps to reproduce: > . Unzip the provided reproduction case and launch a runtime. > . Create a basic family model, populate it with a Man A father of Man B, AND a Man C, > . Create a session, activate the provided Persons viewpoint and create a > diagram > . Open the family tree editor and place the diagram and the editor side by > side > . In the tree editor, set B as father of Man C > . C should appear as a sub node of B in the diagram. Note that if i put
> aql:self.members->select(m | m.father = null and m.mother = null)
as semantic candidates expression of the root mapping PersonMapping, the issue does not occurs.
It might come from the fact that a same semantic element is candidate for a root container and candidate for a sub node of another container at the same time.
|