© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
As you've probably already found some of the groundwork for this is already laid :)
* Mixxx treats loops and cues as the same type at the storage layer (the Cue class is used for storing loops too).
* Cues already have a user-editable label (it's not shown anywhere in the UI though)
* Cues are already mapped to a hotcue slot by the "hotcue" property of Cue.
Also make sure to checkout the very simplistic cue editor in the track properties. You can edit which hotcue a cue is assigned to and its label. It's super clunky though and could really use improvement.
In your other bug regarding a cue list widget you say you'd like to treat loops and cues as the same thing in the UI. It strikes me that that could be confusing in practice if you hit a hotcue and a loop starts. What was your plan re: loops here?