<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Here two personal convictions: <ul> <li>Halo is a kind of meta object for a given Morph, when raised it should be at the top position layer, there should be only one at once. In the past I observed halo falling behind other morph, can't remember exactly the circumstance, I think in the context of Dybo dev </li> <li>Contextual menu requested by the user, should also be raised at a top level position layer, may be a bit behind a halo. In the past I observed menu falling behind the windows (fullscreen) it was invoked from. </li> </ul> Some general though on the issues you raised: <ul> <li>Once a user selected an action from a halo handle, the halo should sink, this will solve one issue you raised, it may brings some other annoyance </li> <li>The dialog issue behind the menu, I see too things:</li> <ul> <li>why the menu is still open once you select an menu entry?</li> <li>if the menu is sticky, for me a problem is a wrong placement of the dialog</li> </ul> </ul> Using property for layer number will likely gives us more flexibility. <div class="moz-cite-prefix">Le 27/05/2025 à 21:35, ken.dickey--- via Cuis-dev a écrit : </div> <blockquote type="cite" cite="mid:19e77822af10686fe4f4ee2bbbfc31b6@whidbey.com">I attached a couple of screenshots. The first one shows a Morph with selection handles, one of which was used to open its menu, and a menu selection of #borderWidth: brought up an edit panel with which to fill in a new value. Note that the halo morphs are above the menu and both are above the fill-in panel. </blockquote> <pre class="moz-signature" cols="72">-- <a class="moz-txt-link-freetext" href="http://mamot.fr/@drgeo">http://mamot.fr/@drgeo</a></pre> </body> </html>