[Cuis-dev] Started Morph Properties HowTo

Hilaire Fernandes hfern at free.fr
Sun Jun 1 00:42:02 PDT 2025


Here two personal convictions:

  * 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
  * 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.

Some general though on the issues you raised:

  * 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
  * The dialog issue behind the menu, I see too things:
      o why the menu is still open once you select an menu entry?
      o if the menu is sticky, for me a problem is a wrong placement of
        the dialog

Using property for layer number will likely gives us more flexibility.


Le 27/05/2025 à 21:35, ken.dickey--- via Cuis-dev a écrit :
> 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.

-- 
http://mamot.fr/@drgeo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20250601/5c685718/attachment-0001.htm>


More information about the Cuis-dev mailing list