Cleared hotcues are not deleted from database
Bug #1653276 reported by
Uwe Klotz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Undecided
|
Ferran Pujol |
Bug Description
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:/
Changed in mixxx: | |
assignee: | nobody → Ferran Pujol (ferranpujol) |
Changed in mixxx: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
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?