-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'temp' slider can be jammed (so that it's not temporary) #4937
Comments
Commented by: deftdawg We clearly need more "spaz" testing.... :P |
Commented by: asantoni There's a problem with the WPushButton controls where if you hold-down left click and then right-click at the same time, you can get them to jam, I believe. Thanks for your bug report. |
Commented by: kousu Hmm. I doubt I right clicked at the same time as left seeing as this was on a Mac. My finger might have brushed ctrl without me noticing but.. yeah I doubt it. Also: The actual effect on the music doesn't necessarily stick (I didn't notice when it stopped sticking), and if it doesn't stick then the button works as expected (as in, mouse-over speeds up, mouse-off goes to normal) so that it's just the colouring of the button that's wrong. |
Commented by: flywitness i can confirm this (extremely ***king annoying) bug. I don't know how to recreate it but it always the reason i have to restart mixxx. |
Commented by: rryan Can't reproduce this in trunk right now. Maybe it's fixed? |
Commented by: rryan ramping pitchbend solved this i think |
Issue closed with status Fix Released. |
Reported by: kousu
Date: 2008-03-13T03:07:04Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp201668
I spaz-clicked the up-temp button on the first player and somehow got it jammed to be on. Now when I click on it it turns off.
I'm guessing there is a flag that gets toggled on mouse clicks over that button, but I seem to have managed to click fast enough that I got in between the updates and now the flag is turned on, right?
MacOS 10,4, Mixxx1.6beta
The text was updated successfully, but these errors were encountered: