Support for "visible" attribute missing in graphical annotation rendering of OMEdit

[Dietmar Winkler]

Currently the presents of visible attributes in an a graphical annotation causes OMEdit to not render that part of the graphical annotation. This kind of limits the possibility to generate semi/dynamic icons.

[Adrian Pop]

We really need an example as we do handle visible if present.
Then we basically ignore it and have consider it as true.

[Dietmar Winkler]

Here a minimal example. If OMEdit would treat visbile as default as true then both rectangles should be visible But they are not:

model IconVisible
parameter Boolean show=true;
equation

annotation(
    Icon(graphics = {
    Rectangle(origin = {-40, 0}, extent = {{-20, 20}, {20, -20}}),
    Rectangle(visible=show,origin = {40, 0}, fillPattern = FillPattern.Solid, extent = {{-20, 20}, {20, -20}})}));
end IconVisible;

[Adrian Pop]

This helps, thanks!

[Dietmar Winkler]

A bit more elaborate test where the tool should actually display always one of the two but the described behaviour of OMEdit would always display both.

model IconVisible
parameter Boolean show=true;
annotation(
    Icon(graphics = {
    Rectangle(visble=not show, origin = {-40, 0}, extent = {{-20, 20}, {20, -20}}),
    Rectangle(visible=show,origin = {40, 0}, fillPattern = FillPattern.Solid, extent = {{-20, 20}, {20, -20}})}));
end IconVisible;

[Francesco Casella]

See also #6250

[Francesco Casella]

Rescheduled to 1.18.0

[sven.baetzing@…]

This feature is very necessary for us at Bosch Rexroth.
We are developeing our libraries of our real products as templates and combine them with parameter files to generate digital twins of our real product portfilio. Therefor one one templates covers alot of variants, which might have different icons. Currently (1.17.0-dev.beta3) all parts with visible attributes are not displayed at all.

So our use case is to change the icon depended of the chosen parameter set (parameter as condition for icon).

[Francesco Casella]

@adrpo, it's now time to tackle this issue together with #2081 and #2661. What do you think?

[Francesco Casella]

Ticket retargeted after milestone closed

[Francesco Casella]

1.18.0 blocker tickets moved to 1.19.0

[Adeel Asghar]

Fixed with instance api.