Skip to content

WTrackMenu: move actions into Auto DJ and Track Files menus#4830

Closed
ronso0 wants to merge 2 commits intomixxxdj:mainfrom
ronso0:autodj-menu
Closed

WTrackMenu: move actions into Auto DJ and Track Files menus#4830
ronso0 wants to merge 2 commits intomixxxdj:mainfrom
ronso0:autodj-menu

Conversation

@ronso0
Copy link
Copy Markdown
Member

@ronso0 ronso0 commented Jun 28, 2022

@github-actions github-actions Bot added the ui label Jun 28, 2022
@daschuer
Copy link
Copy Markdown
Member

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.

@daschuer
Copy link
Copy Markdown
Member

Here is the original discussion:

#1427 (comment)

IMHO the issue that makes it worse is the third "replace" entry. Feel free to remove this.

@daschuer
Copy link
Copy Markdown
Member

"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:

  • Add to Auto DJ (top)
  • Add to Auto DJ (bottom)
  • Add/Load to ...
    ** Player
    ** Sampler
    ** Playlist
    ** Crate
    ** Auto DJ (replace)

What are your most frequent used menu entries?

@ronso0
Copy link
Copy Markdown
Member Author

ronso0 commented Jun 28, 2022

Okay, I expected some discussion : )

Auto DJ top and bottom menu entries are the most used entries during a DJ session

During your DJ session : )
IMO if we want to decide based on such arguments we should make a real survey, not amongst devs.

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.
That's why I repeatedly argued for making the menu configurable.

What are your most frequent used menu entries?

top > bottom = most used > rarely used + (reasons I don't need other options), unmentioned actions never used
In the tracks table ():

  • Open in File Browser
  • Search related tracks
  • Delete Track File
  • Double BPM
  • Hide from Library (oh I can use Del now : )
  • (drag'n'drop for very rare playlist management, don't use crates anymore since I started 'tagging' via comments)
  • (Ctrl+Return opens Properties)

In decks:

  • Delete Track File
  • Search related tracks
  • Adjust ReplayGain from deck gain
  • (open Properties via double click)

I am not motivated to repeat what I wrote on Zulip, I think it's best to discuss details there.
Zulip: Configurable Track Menu
Looking at that right now it seems we won't even reach a concensus to group the file actions :|

@daschuer
Copy link
Copy Markdown
Member

It seems to be a major issue, of two different DJing styles.

  • AutoDJ user: They need Auto DJ top/bottom for almost every track.
  • No AutoDJ user: They open the library track menu only occasionally and are distracted by the useless AutoDJ menu.

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.

@Be-ing
Copy link
Copy Markdown
Contributor

Be-ing commented Jun 29, 2022

How about adding keyboard shortcuts for the "Add to AutoDJ" actions while moving them to a submenu?

@Be-ing Be-ing closed this Jun 29, 2022
@Be-ing Be-ing reopened this Jun 29, 2022
@ronso0
Copy link
Copy Markdown
Member Author

ronso0 commented Jun 29, 2022

How about adding keyboard shortcuts for the "Add to AutoDJ" actions while moving them to a submenu?

We already have all those as [Library],AutoDJAdd....

@daschuer
Copy link
Copy Markdown
Member

With keyboard shortcuts, we have in this case zero visual feedback, which is a usability issue.
... apart from the already overcrowded mapping files.

@daschuer
Copy link
Copy Markdown
Member

A cool solution would be to add buttons to a single menu entry:
"Add to Auto DJ [↑][↓][!]"
I just wonder if we can make this keyboard accessible.

"https://stackoverflow.com/questions/8358965/is-there-a-way-to-add-a-qwidget-to-a-qmenu-in-qtcreator

@ronso0
Copy link
Copy Markdown
Member Author

ronso0 commented Jun 29, 2022

Nice idea, thanks!

maybe the focus issue can be solved:
https://stackoverflow.com/questions/20365663/how-to-control-focus-of-qwidgetactions-child-widgets

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.

@ronso0
Copy link
Copy Markdown
Member Author

ronso0 commented Jun 29, 2022

With keyboard shortcuts, we have in this case zero visual feedback, which is a usability issue.

Well, that is also the case when an AutoDJ action is selected as double-click action.
There is featureIsLoading and featureLoadingFinished. Could be used for a briefly highlighting the AutoDJ sidebar item.

Comment thread src/widget/wtrackmenu.cpp

void WTrackMenu::createMenus() {
if (featureIsEnabled(Feature::AutoDJ)) {
m_pAutoDJMenu = new QMenu(this);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This submenu does not work for me ... we have already discussed better options, that why I request a change.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.....

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does

git reflog 

reveal the old commits? Normally they a still there if you have at least committed them.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ronso0 ronso0 marked this pull request as draft July 4, 2022 20:27
@ronso0 ronso0 closed this Aug 28, 2022
@ronso0 ronso0 deleted the autodj-menu branch August 28, 2022 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants