Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove BPM lock from library column #9978

Open
mixxxbot opened this issue Aug 23, 2022 · 4 comments
Open

remove BPM lock from library column #9978

mixxxbot opened this issue Aug 23, 2022 · 4 comments

Comments

@mixxxbot
Copy link
Collaborator

mixxxbot commented Aug 23, 2022

Reported by: Be-ing
Date: 2020-05-18T15:01:45Z
Status: New
Importance: Undecided
Launchpad Issue: lp1879342


This is a waste of precious horizontal space; there is no need to show it in the library table. Showing it in the library table kinda defeats the point of the lock because it makes it easy to remove the lock on accident.

@mixxxbot
Copy link
Collaborator Author

Commented by: uklotzde
Date: 2020-05-18T16:56:03Z


I use this option frequently when

  • pre-listening to music and adjusting the analysis results and
  • as a quick indicator which tracks have already been adjusted.

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2020-05-18T17:29:17Z


The lock state can be toggled from the track context menu, which is now easy to use from the decks.

  • as a quick indicator which tracks have already been adjusted.

I think this is overloading the lock feature to mean something other than a lock. Isn't there another way that could be indicated? Maybe adding adjusted tracks to a crate/tag? Or adding a library search operator for this? I don't understand why this needs to be taking up space in the library table all the time regardless of whether it is used.

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2020-05-18T17:56:44Z


You can remove the column from the library view if you don't want to see it.

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2020-05-18T18:06:37Z


No, you can't. It's coupled to the BPM column. One solution could be moving the lock to its own column.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant