You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the possibility to define a custom submit button row
support for hotkeys (but I guess this should be more of a general feature ...shall we create a separate issue for that -> binding hotkeys to buttons and other UI elements ?)
stacking of model dialogs (although from an ux perspective this is often an anti-pattern but there might be some usecases where stacking is helpful)
Good ideas! I think the dialog should work like a Panel (it can have shadow and a box around it with a title if using the latter option), but with the additional feature of having a button bar at the bottom (can be customized) and it blocks interaction with other components on the screen.
So the things you suggested are fine for a basic implementation but I think that stacking should be an enhancement later (if feasible). I was thinking about how the implementation should look like. Since a dialog should handle its own focus I think that behind the scenes a dialog should be a Screen with transparent background (because it has its own focus handling).
Currently we use
ComponentsLayerable
:which composes a simple
Layerable
and aContainer
to manage bothComponent
s and simpleLayer
s.This should be improved by having a stack of
Layerable
s:Component
sComponent
s should beModalComponent
s which have a size of the screen so the user can't interact with ordinaryComponent
s below a modal.Layer
s.Things to do:
addModal
next toaddComponent
toComponentContainer
.CompoentContainer
instead of what we have now inTileGridScreen
DefaultComponentContainer
into its own classThe text was updated successfully, but these errors were encountered: