WTrackMenu: move actions into Auto DJ and Track Files menus#4830
WTrackMenu: move actions into Auto DJ and Track Files menus#4830ronso0 wants to merge 2 commits intomixxxdj:mainfrom
Conversation
|
I am strongly against this because the Auto DJ top and bottom menu entries are the most used entries during a DJ session. I cannot effort the extra mouse move to a sub menu. |
|
Here is the original discussion: IMHO the issue that makes it worse is the third "replace" entry. Feel free to remove this. |
|
"Add to Auto DJ (Replace)" has been introduced here: https://bugs.launchpad.net/mixxx/+bug/1566206 This will work for me, not sure if anyone else uses the other load functions often, I don't use them at all:
What are your most frequent used menu entries? |
|
Okay, I expected some discussion : )
During your DJ session : ) However we will always find someone how "really needs" this and that option, and we will get nowhere but add more and more legitimate actions to the top level of the menu.
top > bottom = most used > rarely used + (reasons I don't need other options), unmentioned actions never used
In decks:
I am not motivated to repeat what I wrote on Zulip, I think it's best to discuss details there. |
|
It seems to be a major issue, of two different DJing styles.
I do have not auto DJ enabled all the time, but I use I use auto DJ all the time to collect possible follow ups. Instant followers I load via double click. I do not use four decks for staging tracks. A servery does not really help here, because we already know that both groups exists and who wants to judge how many percentage rectifies of introducing a regression. If the distraction by Auto DJ menu entries is such big that, it rectifies something configurable, or a fancy menu with buttons to put all in one line, or a library column or such, go ahead. |
|
How about adding keyboard shortcuts for the "Add to AutoDJ" actions while moving them to a submenu? |
We already have all those as |
|
With keyboard shortcuts, we have in this case zero visual feedback, which is a usability issue. |
|
A cool solution would be to add buttons to a single menu entry: "https://stackoverflow.com/questions/8358965/is-there-a-way-to-add-a-qwidget-to-a-qmenu-in-qtcreator |
|
Nice idea, thanks! maybe the focus issue can be solved: fwiw I once looked into QWidgetAction to resolve the styling / focus issue (keyboard vs. mouse focus) with the checkable items in the crate menu, but the conversion wouldn't have been worth the effort. |
Well, that is also the case when an AutoDJ action is selected as double-click action. |
|
|
||
| void WTrackMenu::createMenus() { | ||
| if (featureIsEnabled(Feature::AutoDJ)) { | ||
| m_pAutoDJMenu = new QMenu(this); |
There was a problem hiding this comment.
This submenu does not work for me ... we have already discussed better options, that why I request a change.
There was a problem hiding this comment.
sure. I considered that option off the table by now anyway, the QWigetAction with 3 buttons is much better if we can make it work.
I made a prototype earlier, it works nicely with only minor changes to the AutoDJ slots. Didn't check the focus behavior and styling, yet. Should be manageable though
There was a problem hiding this comment.
I already had a working prototype with the [↑] [↓] [!] buttons, even some focus/navigation issues solved ~90%.
and now I can't find it anymore... carelessly cleaned up git stash or local branches?
meeeh.....
There was a problem hiding this comment.
does
git reflog
reveal the old commits? Normally they a still there if you have at least committed them.
There was a problem hiding this comment.
this didn't point to any usable commit, just [sha1] HEAD@{xxxx}: checkout: moving from trackmenu-autodj-buttons to search-date-span logs, but at least that revealed the branch name.
What helped was creating .git/lost-found.txt with
git fsck --full --no-reflogs --unreachable --lost-found | grep commit | cut -d\ -f3 | xargs -n 1 git log -n 1 --pretty=oneline > .git/lost-found.txt
in there I found the last commit, git checkout [sha1]
et voilà, back ontrack!
Thanks for the hint @daschuer
There was a problem hiding this comment.
https://mixxx.zulipchat.com/#narrow/stream/247619-UI-.26-UX-design/topic/Configurable.20Track.20Menu