Opened 11 years ago

Closed 11 years ago

#7359 closed defect (fixed)

can't bind function keys (F1..F12) or use already bind ones

Reported by: Markus Schulz <msc@…> Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: MythTV - General Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

if i try to bind a Fx Key to a function nothing happens on pressing Fx. Looks like the key would not be recognized. xev reports them fine: KeyPress? event, serial 34, synthetic NO, window 0x6000001,

root 0x13c, subw 0x0, time 156387359, (355,138), root:(1226,653), state 0x10, keycode 67 (keysym 0xffbe, F1), same_screen YES, XLookupString gives 0 bytes: XmbLookupString? gives 0 bytes: XFilterEvent returns: False

KeyRelease? event, serial 34, synthetic NO, window 0x6000001,

root 0x13c, subw 0x0, time 156387479, (355,138), root:(1226,653), state 0x10, keycode 67 (keysym 0xffbe, F1), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False

and all other applications can use them. i'm using QT from debian/sid (4:4.5.3-4) with USB (Logitech) and Keystone (Bluetooth) keyboards.

Change History (2)

comment:1 Changed 11 years ago by sphery

(In [22634]) Refs #7359. Don't assume that Qt::Key enum values are in any particular order--because the order can (and did) change with Qt versions.

Modifier keys are no longer grouped together tightly. Therefore, when trying to ignore modifier key presses by ignoring all keys between Qt::Key_Shift (0x01000020) and Qt::Key_AltGr (which changed in Qt4 to 0x01001103), we were ignoring far too many keys--including the Function keys.

comment:2 Changed 11 years ago by sphery

Resolution: fixed
Status: newclosed

(In [22635]) Fixes #7359. Fix key grabbing in MythControls?. Backports [22634] from trunk.

Note: See TracTickets for help on using tickets.