Comment 21 for bug 1969634

currently Mixxx uses many commands to do almost the same thing (move between folders, files and track data).
This implies that if I want to manage the Mixxx through a console, the console should have many buttons and traxes dedicated to just that.

I would like to propose to create a command that brings together as many functions as possible:
through a trax (or by pressing a key several times), you can change focus (move_focus), but not only "resources" <==> "library", but be able to focus every part of Mixxx (deck1, deck2, settings, master ...).
each part, when selected with the "GoToItem" button, can in turn be navigated through the usual trax or button and you can still select the object using the "GoToItem" button/command, or return to the upper level with the button/command (example:) "return".

through a drop-down menu (for example in the settings), list all the parts of Mixx that can be focused via trax or button, being able to flag them in order to eliminate the parts in which you do not want to navigate, including the submenus (at inside Deck1, to be able to flag "hotcue" so you can use them via "GoToItem", but maybe not flag "beatjump" so as not to waste time scrolling through the parts I know I never want to use via "GoToItem").

in this way, for example, I could choose, with the trax or the button, to navigate inside deck1 to scroll to the "Hotcue3" button
and set it using the "GoToItem" button; or set through "GoToItem" the command "loop_activate" of Deck2 ...
if I focus on the library, the trax or the button would scroll the columns .. etc

in this way, however, "GoToItem" could no longer be used to load a track from the library, because when pressed it would put the column in focus in ascending / descending order

keep in mind that more and more consoles come out with 6/8/.. settable midi buttons (+ "shift" buttons) and maybe even with trax
(I hope google translate did its job well)