Reassigning hotcue might result in lost cue point

[Ferran Pujol]

EDIT:
Mixxx can already change the hotcue assignation of a cue point. However, if a cue point is assigned to a hotcue that is already assigned to another cue point, the old cue is not set to cue point -1. This causes that on restart, the old cue is deleted instead of just assigned to no hotcue.

----

Skins usually show less hotcue buttons than cue points a user can set. Thus, Mixxx should allow a reorder or swap position function for cue points to allow the user to place his/her preferred cue points in front.

Edit: In fact, order and hot-cue assignation should be independent. Hotcues should support swapping e.g. make hotcue1->hotcue2 and hotcue2->hotcue1. Also, in the cue editor of the track properties, the list should allow the user to sort displayed cues by hotcue assignment, time and/or name.

[RJ Skerry-Ryan (rryan)]

Hm maybe I'm misunderstanding what you mean but order of the track's cue list is already independent from hotcue assignation. You can re-order the cues list without affecting which cue is loaded in each hotcue slot. The hotcue property of the Cue class determines which hotcue slot a cue is assigned to.

[Ferran Pujol (ferranpujol)]

Yeah what you say is the clarification I wanted to make.
In my first description I was assuming that the cues have an inherent order (they have an ordinal property) and that the n first cues are the ones assigned to the n hotcues. This was obviously wrong.

[Ferran Pujol (ferranpujol)]

I've rephrased the bug.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/7576