Hi Ronso, thank you for responding.
I have already attempted to track the states of the sidebar/table. I was successful in being able to independently control the sidebar and the track list using only the rotary selector.
The main issue I encountered is when you accidentally long-press on the rotary selector to switch to the other frame; if you do that on a branch that contains no tracks (eg: Top->Crates), it caused an issue.
Another issue is if someone were to click on a different pane, the script would become out-of-sync.
For some reason as well, my code got screwed up when trying to implement the long-press, and now I have to double-click the rotary selector to traverse branches, so I’ll have to look at that. LOL.
I agree with your solution, creating Mixxx-internal equivalents, and understand that’s probably not going to happen. I guess what I don’t understand from your response is when the new QML skinning system is created, whether this functionality might become part of that. The feeling I’m getting is that no one will do it for v2.3, or future versions until the new skinning system is done, and then maybe; feel free to correct me.
I’m considering preparing my system to compile Mixxx v2.3, and learning how to add the functionality, using the existing functionality as an example. Maybe this could help/be ported forward for future versions. When I consider the advantages and disadvantages of doing it either way (keyboard equivalent vs. the way that works for my use case), I believe that the keyboard equivalent could be problematic for Windows users if a window pops up and steals focus in the middle of a set. Could be beneficial. It could be my contribution, as small as it is.
Is there anything I need to know about Mixxx’s contribution policies before I give it a try?