Opened 4 years ago
Closed 8 months ago
#6111 closed defect (fixed)
Support for "visible" attribute missing in graphical annotation rendering of OMEdit
Reported by: | dietmarw | Owned by: | adrpo |
---|---|---|---|
Priority: | blocker | Milestone: | 1.21.0 |
Component: | OMEdit | Version: | v1.16.0-dev |
Keywords: | Cc: |
Description
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.
Change History (12)
comment:1 Changed 4 years ago by adrpo
comment:2 Changed 4 years ago by dietmarw
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;
comment:3 Changed 4 years ago by adrpo
- Component changed from OMEdit to NF API
- Owner changed from adeas31 to adrpo
- Status changed from new to accepted
This helps, thanks!
comment:4 Changed 4 years ago by dietmarw
- Component changed from NF API to OMEdit
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;
comment:5 Changed 4 years ago by casella
- Milestone changed from Future to 1.17.0
- Priority changed from high to blocker
comment:6 Changed 3 years ago by casella
See also #6250
comment:7 Changed 3 years ago by casella
- Milestone changed from 1.17.0 to 1.18.0
Rescheduled to 1.18.0
comment:8 Changed 3 years ago by 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).
comment:9 Changed 3 years ago by casella
comment:10 Changed 3 years ago by casella
- Milestone 1.18.0 deleted
Ticket retargeted after milestone closed
comment:11 Changed 3 years ago by casella
- Milestone set to 1.19.0
1.18.0 blocker tickets moved to 1.19.0
comment:12 Changed 8 months ago by adeas31
- Milestone changed from 1.19.0 to 1.21.0
- Resolution set to fixed
- Status changed from accepted to closed
Fixed with instance api.
We really need an example as we do handle visible if present.
Then we basically ignore it and have consider it as true.