keyboard-input is event-based

Bug #367146 reported by Nick on 2009-04-26
2
Affects Status Importance Assigned to Milestone
Mixxx
Low
Unassigned

Bug Description

The cue button on the keyboard doesn't work like it should. If you hold it you get an almost-stutter because it is receiving keyboard repeats which each trigger the button which make it jump back. The root of the problem is that mixxx is reading keyboard -events- instead of polling the keyboard directly.

Nick (kousu) on 2009-04-26
description: updated
summary: - keyboard-input is event-based, not polling-basedIf you don't find
- anything there, first try a few searches on various keywords related to
- the problem to see if it's already been reported in the bug tracker and
- what the current status is. If you find one or more that relate, click
- change on “This bug doesn't affect me” to “vote” for the bug (you may
- need to sign in to see this.If you don't find anything there, first try
- a few searches on various keywords related to the problem to see if it's
- already been reported in the bug tracker and what the current status is.
- If you find one or more that relate, click change on “This bug doesn't
- affect me” to “vote” for the bug (you may need to sign in to see this.)
+ keyboard-input is event-based
RJ Skerry-Ryan (rryan) on 2010-06-21
Changed in mixxx:
status: New → Confirmed
importance: Undecided → Low
milestone: none → 1.8.1
Bill Good (bkgood) wrote :

Albert fixed this in http://bazaar.launchpad.net/~mixxxdevelopers/mixxx/release-1.8.x/revision/2458 (this was bugging me too).

Polling would actually have made this a more difficult fix (speaking from doing input polling in video games, yuck), luckily Qt has a pretty flexible event subsystem.

Changed in mixxx:
status: Confirmed → Fix Committed
RJ Skerry-Ryan (rryan) on 2010-09-22
Changed in mixxx:
milestone: 1.8.1 → 1.8.0
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