Summary: | The move of mapping specifications impacts the external references from other odesign files | ||||||
---|---|---|---|---|---|---|---|
Product: | [Modeling] Sirius | Reporter: | Cedric Notot <cedric.notot> | ||||
Component: | Properties | Assignee: | Project Inbox <sirius.properties-inbox> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | pierre-charles.david | ||||
Version: | 6.3.0 | Keywords: | triaged | ||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Cedric Notot
2020-04-30 06:11:12 EDT
Created attachment 282632 [details]
Example on basicfamily
On this example, you get GroupOverride from the extension.odesign which overrides DefaultGroup from test.odesign. This last one is used by the DefaultPage.
If you move DefaultGroup to the top down (after DefaultGroup2) then it is DefaultGroup2 which becomes overridden (not used by DefaultPage).
Agreed, but this is a general issue with the VSMs, which could only be fixed by very deep and impactful changes in how their elements are identified. Unless it becomes blocking for very common scenarios *and* we find a way to fix it which is not too risky (in terms of compatibility especially), I suspect we will never be able to change this. |