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
I was wondering whether having the State refactored as a QtObject would make sense, in that it would add it the possibility of emitting signals to synch the GUI. This would make easier to glue together different widgets that see each other only through the state. All the widgetish things will still be out of it, so this would preserve the distinction between the state and the user interface, but might streamline some parts of the code.
The text was updated successfully, but these errors were encountered:
I was wondering whether having the State refactored as a
QtObject
would make sense, in that it would add it the possibility of emitting signals to synch the GUI. This would make easier to glue together different widgets that see each other only through the state. All the widgetish things will still be out of it, so this would preserve the distinction between the state and the user interface, but might streamline some parts of the code.The text was updated successfully, but these errors were encountered: