Cleared hotcues are not deleted from database

[Uwe Klotz]

Cleared hotcues don't get deleted from the database. Instead they are kept in the table 'cues' with a 'hotcue' index of -1 forever. Those dead hotcues are implicitly ignored. They just waste memory and need to be skipped when iterating through the cues of a track.

This is a follow-up of the following PR:
https://github.com/mixxxdj/mixxx/pull/1098

[Daniel Schürmann (daschuer)]

It is implemented like that, because it was planned that it is possible to assign a cue control to one of many cues. In this case it is correct to not delete the cue.
In the most common case that the cue was set by the cue control, it should be removed.

@Ferran: How does it fit to your plans?

[Ferran Pujol (ferranpujol)]

I think we should delete cuepoints when they are unassinged from a hotcue by now.

If we ever support unassigned cuepoints, I think the right way to create them is with the track properties pane or the dedicated cue-point manager list or whatever.

[Ferran Pujol (ferranpujol)]

Fixed in https://github.com/mixxxdj/mixxx/pull/1532

[Swiftb0y (swiftb0y)]

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