Community
Participate
Working Groups
In EEF both concepts are named with the suffix "Expression"
Both concepts should be renamed in Sirius and treated as InterpretedExpression because they already have this behavior (you can use the various interpreters available in those properties).
New Gerrit change created: https://git.eclipse.org/r/80209
Gerrit change https://git.eclipse.org/r/80209 was merged to [master]. Commit: http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/commit/?id=75605cbc17cb132c6daa8b516f1787cb29f9a896
Hi Stéphane, could you add a validation scenario/model ?
Steps to reproduce: 1. Create a VSM with a Properties View Description. 2. Inside a Group, create a widget (for example a Text), and an explicit Style element for it. 3. The style should have "Font Name Expression" and "Font Size Expression" attributes, in yellow background and behaving like an expression field. 4. Configure both expressions to return dynamic values depending on some property of the semantic element, and test that the font and the text size are properly updated at runtime depending on the state of the semantic model.
No use case to reproduce problem. Thanks to add a use case or a link to a use case to reproduce problem. Waiting, issue is reopened.
Created attachment 264668 [details] Sample project to reproduce the bug Steps to validate: 1. Import the attached project and open it. 2. In the model explorer or in the diagram, select classes A, then B. 3. Note that both the font and the text sizes of the "Name" field in the properties view changes between A and B, consistent with the conditions set in the VSM. 4. Select A, in the properties view rename i into C, and notice how the font and text size are dynamically updated to match the expressions in the VSM.
Available in Sirius 4.1.0, see https://wiki.eclipse.org/Sirius/4.1.0 for details.