control aliasing for legacy support
Bug #1273953 reported by
RJ Skerry-Ryan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
Wishlist
|
Nicu Badescu | ||
Bug Description
Sometimes we make mistakes in how we name things. For example, we named used the group [Microphone] before we knew we wanted the option of multiple microphones so we should have started with [Microphone1]. We can fix this problem for legacy skins/controllers by renaming the control and then creating an alias for the control under the legacy name.
| Changed in mixxx: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
Revision history for this message
| Nicu Badescu (badescunicu) wrote | #1 |
| Changed in mixxx: | |
| assignee: | nobody → Nicu Badescu (badescunicu) |
| status: | Confirmed → In Progress |
Revision history for this message
| Nicu Badescu (badescunicu) wrote | #2 |
Revision history for this message
| Daniel Schürmann (daschuer) wrote | #3 |
| Changed in mixxx: | |
| status: | In Progress → Fix Committed |
| milestone: | none → 1.12.0 |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #4 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
Ryan, do you have any ideas how we should approach this?