I wonder how this should interact with Qt's "enabled" state for widgets.
* Widgets that are not enabled do not receive mouse / other input events.
* Children of a disabled widget are also disabled.
We could use this to our advantage if every widget supported rendering a "disabled" state version of itself. Today only WDisplay/WKnob support this.
If we wanted to disable portion of the GUI, like the EQs or the mixer, we could simply have a control that indicates the enabled state and connect that control to the enabled state of the WWidgetGroup containing all of those controls. The whole section would automatically switch its enabled/disabled state with changes of that control.
I wonder how this should interact with Qt's "enabled" state for widgets.
* Widgets that are not enabled do not receive mouse / other input events.
* Children of a disabled widget are also disabled.
We could use this to our advantage if every widget supported rendering a "disabled" state version of itself. Today only WDisplay/WKnob support this.
If we wanted to disable portion of the GUI, like the EQs or the mixer, we could simply have a control that indicates the enabled state and connect that control to the enabled state of the WWidgetGroup containing all of those controls. The whole section would automatically switch its enabled/disabled state with changes of that control.