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

Crates sorted differently in Tree and context menu #9546

Closed
mixxxbot opened this issue Aug 23, 2022 · 2 comments · Fixed by #11023
Closed

Crates sorted differently in Tree and context menu #9546

mixxxbot opened this issue Aug 23, 2022 · 2 comments · Fixed by #11023

Comments

@mixxxbot
Copy link
Collaborator

Reported by: ronso0
Date: 2018-12-13T17:04:51Z
Status: Confirmed
Importance: Medium
Launchpad Issue: lp1808387


Appearantly special charcters in crate names are treated differently in Crate tree and tack context menu.

I have crates named like sub-genres and used whitespaces and special characters to have them sorted by mood/energy and not alphabetically.
For sub-genres this doesn't really bother me, but I have crate names like '_____samples' to force-push them to the top of the crates list.

Crate list sorting (numbers are just for illustration):
1 ___samples
2 .FiDT
3 JukeFooT easY Jazzz
4 JukeFooT PRO
5 JukeFoot Deeep
6 JukeFooT reAL

Context menu sorting:
2 .FiDT
4 JukeFooT PRO
3 JukeFooT easY Jazzz
6 JukeFooT reAL
5 JukeFoot Deeep
1 ___samples

It seems the crate list uses this sorting

  • .
  • _
  • numbers
  • letters, alphabetically & case-independent

Whereas the context menu sorts like this

  • .
  • 0-9
  • A-Z
  • _ (several '' are regarded as one '')
  • a-z

master 2018-12-13

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2020-12-06T17:02:50Z


reported for 2.3 beta
https://i.imgur.com/UPeaGmp.png

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@Russe
Copy link
Contributor

Russe commented Oct 29, 2022

I can see this issue also with playlists.

@ronso0 ronso0 linked a pull request Oct 29, 2022 that will close this issue
@ronso0 ronso0 closed this as completed Oct 31, 2022
@ronso0 ronso0 added this to the 2.3.4 milestone Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants