Setting a hot cue fires valueChanged() for all of them
Bug #599765 reported by
Sean M. Pappalardo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
Medium
|
RJ Skerry-Ryan | ||
| 1.8 |
Fix Released
|
Medium
|
RJ Skerry-Ryan | ||
Bug Description
When one hot cue is set or cleared, valueChanged() is fired for all of the hot cues, causing a noticeable delay and flickering of the controller's LEDs. It gets worse if you repeatedly clear and set hot cues on a controller. (The SCS.3d script now lights the hot cue point LEDs by watching the "hotcue_x_enabled" ControlObjects as of r2452 of the 1.8 branch.)
Also, and this may be related, there is still a large amount of data qDebugged when a hot cue is manipulated. Please remove that.
Related branches
lp://staging/mixxx/1.8
(Merged)
| Changed in mixxx: | |
| milestone: | 1.8.0 → none |
| status: | Confirmed → New |
Revision history for this message
| RJ Skerry-Ryan (rryan) wrote | #1 |
| Changed in mixxx: | |
| status: | New → Fix Committed |
| assignee: | nobody → RJ Ryan (rryan) |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #2 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
Rewrote the hotcue update method so that this doesn't happen, also removed the noisy qDebugs.