Dual screen Skin

Can you express this idea in more detail?

Dual screens are pretty common but also i see the usability of a single screen split.
I believe we already have a WISHLIST bug (cant find atm) for a detachable library window, something like e.g. Deckadance has for quite some time. Is something like that the reason for your idea?

Could not find a bug like this too, so here is a new one.

A simple and easy to achieve solution would be an independent library window.

A High End solution would be to have two single skin-able windows to allow setups like this:
http://www.youtube.com/watch?v=P3QhZuHbAUY

Today you get nearly only Widescreen-Displays, so could be a real benefit for pre-mixing, radio, etc.

Another Idea:
Left Display: 4 Decks with 4 horizontally Waveforms like "Latenight"-Skin
Right Display: 8-12 "full-featured" SampleDecks at top and the library at bottom

I would propose supporting this with a <Window> tag in the skin that acts like a <WidgetGroup> except has no parent (this way it would show as its own window rather than be rooted in the parent).

<Window>
  <Children>
    .. skin widgets as normal ..
  </Children>
</Window>

Getting that working would be pretty easy. But then making it interact well with other windows (i.e. letting the master window show/hide other windows) would be teh bulk of the project. I think it could be done with a skin-created CO connected to the Window 'visible' property.

The way you propose to do this is probably an intermediate quick solution, but not what I have in mind when talking about multiple-windows interface.

Ideally, the multiple windows interface is not hardcoded by the skin but rather each section of the skin can be assigned to whatever window the user want. by section I mean "library", "deck1" to "deck4", "mixer", "effects", "mic/aux" and "sampler".

This way, there is only one skin for mono and multi window and this is suitable to each use-case, the user choose its layout.

That would be nice... In the current skin/widget system however I predict that is going to be pretty difficult. It's kind of at a breaking point and probably needs replacing.

(and eventually we'd want to use this type of system for advanced controllers that have built-in displays, too)

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6940