|
Re: Sirius Tree Description [message #1804217 is a reply to message #1804209] |
Wed, 20 March 2019 15:30 |
|
Hello,
Concerning your first question, as you said the order is defined by the order of the mappings. If you want different type of elements to be displayed, you will need to have only one mapping where the Domain Class will be a common superclass (the Domain Class can be an abstract class) and a semantic candidate expression that return the element in this order. This may implies change in your metamodel to have this level of abstraction. For exemple, let's say that we have a family metamodel. If your metamodel has 3 class Family, Man and Woman where Family has 2 references men and women, then in your odesign you are stuck with 2 mappings, one for Man and one for Woman and they will be displayed separatly. Instead you update the metamodel with 4 class Family, FamilyMember, Man and Woman where Man and Woman inherits FamilyMember and Family only has 1 reference familyMembers. In your odesign under Family, you don't have 2 mappings but only one on FamilyMember and the members will be presented in the order of creation instead of one kind after the other.
I am not sure to understand your second question. The order of the elements displayed by a mapping is determined by the semantic candidate expression. The order displayed should be the same has the order serialized in the aird file.
Regards,
Steve
Steve Monnier - Obeo Canada
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
|
Re: Sirius Tree Description [message #1804263 is a reply to message #1804219] |
Thu, 21 March 2019 13:23 |
|
Hello,
You do not need a fake level, you just need a mapping (and a submapping for your sublevel) with a domain class and semantic candidates expression matching all the element you want to present. The semantic candidates expression can be a reference (even derived if needed) an EOperation or a service.
If in your semantic model the sub-sections are listed in alphabetical order instead of the creation order, you must have changed how element are indexed in your metamodel or by custom code I guess. If in your odesign the semantic candidate expression calls the same process then it will be displayed in the same order. The displayed order does not have to be the same as the semantic order.
If when you add a new element, you need to refresh to have the element move to its correct position, you may be in manual refresh. Can you check in Preference/Sirius if the Automatic refresh property is checked. If it's in automatic refresh, it's strange but you can force having a refresh by checking the "force refresh" property on the creation tool of your Tree Description in the odesign file.
Regards,
Steve
Steve Monnier - Obeo Canada
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
Powered by
FUDForum. Page generated in 0.04430 seconds