Setting a hot cue fires valueChanged() for all of them

Bug #599765 reported by Sean M. Pappalardo on 2010-06-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Medium
RJ Skerry-Ryan
1.8
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

Changed in mixxx:
milestone: 1.8.0 → none
status: Confirmed → New
RJ Skerry-Ryan (rryan) wrote :

Rewrote the hotcue update method so that this doesn't happen, also removed the noisy qDebugs.

RJ Skerry-Ryan (rryan) on 2010-09-11
Changed in mixxx:
status: New → Fix Committed
assignee: nobody → RJ Ryan (rryan)
RJ Skerry-Ryan (rryan) on 2010-10-05
Changed in mixxx:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers