Hi everyones,
We noticed inconsistencies when deactivating a viewpoint in a given context. Activation is not a problem.
We propose the specification of the behavior of a deactivation of a viewpoint for the next release of papyrus.
Warning, this is not a specification of a context switch inside architecture framework. It is much more complex and impacting and need also to be specified.
If you have comments, they are welcome.
Viewpoint deactivation
1. Invariant
· Language
o Profiles are applied
o ElementTypes are active
o Graphical element types are active
o New child
2. Difference
· List of possible tables/diagrams are not the same
3. Which behavior
· Diagrams, Tables that are not listed in active viewpoint shall be visible in ModelExplorer with grayed icon.
· Diagrams, Tables that are not listed in active viewpoint shall be visible in WelcomePage with grayed icon.
· Diagrams, Tables that are not listed in active viewpoint shall be visible Hyperlink (and table of diagrams) with grayed icon .
· Model user shall not be able to open the Diagrams, Tables that are not listed in active viewpoint.
· When Model user want to open Diagrams, Tables that are not listed in active viewpoint, papyrus shall propose to the model user to activate the viewpoint that list wanted diagrams or tables.
· When the model user deactivates a viewpoint, papyrus shall close diagrams /table corresponding to this deactivated viewpoint
· When the model user deactivates a viewpoint, papyrus shall refresh Menu new diagram/table corresponding to this activate viewpoint
Papyrus Team
