Menus, popups and toasts
· 2 min read
Menus are scene nodes now. A menu holds rows, any widget names one as its
context, and a toast says something and leaves.

- A menu bar is a
rowofmenunodes. A row that is itself amenuopens to the side on hover, one submenu at a time, and does not shut the menu it hangs off. - Any widget names a
menuas itscontext. A right click opens it at the pointer, and so does a long press, which is the same gesture on a phone. The widget's ownon_clickstays quiet for that press. placementsays where a menu opens:below,above,pointer, orcenter.shortcutis a chord on any widget, written one way:cmd+shift+s,f5. A menu row fires with its menu shut, and the row draws the chord the way this platform writes it.- A
toastis a root that stacks at its anchor, fades over its last half second, and frees itself when itsdurationis up. A binding action puts one up with no script at all. - A
dialogcloses on Escape and on a click on the dim, and reports that throughon_change.
Every one of them is a property on the widget component, so the inspector
edits them and a scene file holds them.
The rest is on the roadmap.
