Mixxx 2.2.0 (LateNight skin): chosen controls get unchecked/removed if they won't "fit" on limited-resolution screen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Committed
|
Undecided
|
ronso0 |
Bug Description
I'm not sure if this is WISHLIST, BUG or INTENDED BEHAVIOR. I'm running Mixxx on a laptop with limited screen resolution. My lappy screen resolution is only 1366x768. The LateNight skin automatically unchecks/removes controls, like MIC/AUX or SAMPLERS, when screen resolution or available screen real-estate won't allow all my chosen controls to "fit" in the Mixxx window. For example, if I attempt to display the MIC/AUX controls and the SAMPLER controls, without putting MIXXX into FULLSCREEN first, the LN skin will allow me to display either of those controls, but not both. The LN skin will disable the other control if I attempt to display both of them at once. Another example: if I am running MIXXX in FULLSCREEN, to allow all my chosen controls to fit, and I switch out of FULLSCREEN, the controls get removed/unchecked, because they no longer "fit" in the Mixxx window. When I switch back to FULLSCREEN, the controls are not displayed again. They remain unchecked/removed. This behavior may be as-designed, but it is somewhat annoying/
I'd say this behaviour is party intended and partly a bug:
the lower half was constructed this way to avoid squeezed samplers or Mic units, but the settings don't persist when the skin get's resized/redrawn or when Mixxx gets restarted.
Other skins don't have this 'protective' mechanism, so how to proceed?
a) We could allow to enable all widgets regardless of the available screen space, some widgets get squeezd and users need to decide what to resize (waveforms, less FX units) or what to disable so everything fits nicely.
b) IDK how difficult it is to put FX units, samplers & Mic/Aux into a scrollarea. Also I'm not sure if a scrollarea would improve the UX significantly: unlike the library, it's tricky to use touchpad or scroll wheel inside that area since (while scrolling) users might accidentially hover knobs or sliders which would then catch the scroll events.
So IMO a) is the way to go (for now).