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
In previous versions of GTK, logic around menu actions and popups was done via widget signals, and so this logic tended to live inside the widgets that made use of them.
In GTK4, whenever we see popup menu actions or accelerators, they should be implement by creating actions. In many cases it's appropriate to actually move these actions closer to objects implementing the program or at least application logic rather than the UI logic. I would guess that almost all of the actions in the main menu are better moved to BtEditApplication.
The text was updated successfully, but these errors were encountered:
I suspect it'll be fine... The set of application-level actions are fairly
limited (like File/Open) and there are still a quite big set of actions
that are appropriately handled in the UI controls. Those are things like
updating zoom levels in machine view, etc.
Of course, if it gets large then one possibility is to break it out into
something like a BtAppActionsHandler.
#133
Please take a look at this: https://docs.gtk.org/gtk4/actions.html
In previous versions of GTK, logic around menu actions and popups was done via widget signals, and so this logic tended to live inside the widgets that made use of them.
In GTK4, whenever we see popup menu actions or accelerators, they should be implement by creating actions. In many cases it's appropriate to actually move these actions closer to objects implementing the program or at least application logic rather than the UI logic. I would guess that almost all of the actions in the main menu are better moved to BtEditApplication.
The text was updated successfully, but these errors were encountered: