A minor OMEdit glitch regarding selection of a lower layer object

[anonymous]

Consider the following model:

model test
  annotation(Diagram(coordinateSystem(extent = {{-100, -80}, {100, 80}}, preserveAspectRatio = true, initialScale = 0.1, grid = {2, 2})), Icon(coordinateSystem(extent = {{-100, -80}, {100, 80}}, preserveAspectRatio = true, initialScale = 0.1, grid = {2, 1}), graphics = {Rectangle(origin = {2, 1.5}, fillColor = {0, 255, 255}, fillPattern = FillPattern.Solid, extent = {{-56, 16.5}, {56, -16.5}}), Ellipse(origin = {-54, 0.5}, fillColor = {255, 255, 0}, fillPattern = FillPattern.Solid, extent = {{-18, 28.5}, {18, -28.5}}, endAngle = 360), Ellipse(origin = {62, 1.5}, fillColor = {255, 255, 0}, fillPattern = FillPattern.Solid, extent = {{-18, 28.5}, {18, -28.5}}, endAngle = 360)}));
end test;

When, clicking on the rectangle (in icon view) the user has no visual feedback that the rectangle is selected, since the red squares are hidden by the circles.

Maybe the red squares indicating selection must stay always on top? This is how Dymola works.

[Adeel Asghar]

This is not possible since the red boxes are children of rectangle or circle. We can only set stacking between the items that are at same level. I don't know how Dymola is doing it, perhaps it also draws the red boxes at the same level where rectangle is and not as its children.

I added support for changing shapes stacking order 1f6c73/OMEdit via the context menu of the shape. Right click the rectangle and click on Bring to Front. The rectangle is shown on top of the circles, resize it and then put it back via Send to Back.

[Dietmar Winkler]

Sorting away the closed as invalid, won't fix and duplicate tickets from Future.