[mythtv] usability bug in mythfrontend

[Micah F. Galizia]

On Tue, 2005-28-06 at 19:44 -0400, Keith Irwin wrote:
> On Tuesday, June 28, 2005, at 07:32  PM, Micah F. Galizia wrote:
> 
> >> 1) I would imagine that most people with a real remote
> >> (i.e. with a channel up and down button) would have done this?
> >
> > Actually, if you use the Linux input layer, the channel up/down
> > scancodes are 402 and 403.  XInput, allowing scancodes no greater than
> > 255, is incapable of receiving those keys.  Probably works fine for 
> > LIRC
> > though.
> 
> I believe that those are actually the key codes, not scan codes.  
> There's generally a two part translation: scan codes -> key codes -> 
> characters.  So far as I can tell there is no program for X or tty 
> which actually handles key codes above 255.  As I couldn't get lirc 
> working, I wound up hacking the gpio ir-kbd drivers (which produce key 
> codes rather than scan codes) to produce key codes in the 0-255 range.  
> This was the only way I could get my remote working.  It's not a mythtv 
> problem, obviously, but it is a big pain.  It may also be something 
> that we could adjust mythtv to fix since X applications do not have to 
> use xkb's key mappings.  I looked at fixing xkb to handle it, but the 
> assumption that a key code is just one byte seemed to be embedded all 
> over the place.  There were one byte types, 255's and 0xff's in a 
> number of places throughout the code.  The whole thing was really 
> sloppy.

Key codes, yes, my bad.

> If anyone has a better idea on how to fix this without hacking the 
> drivers, please let me know.  I'll probably look at a mythtv specific 
> solution at some point in the future when I have more time.

Although this is a magnificent rehash of the past, I'm going to add
Input layer support directly to myth.  This time (yes, last time it
didn't go over so well), I'm going to do it as a plugin.  I figure that
I should be done by the end of next week (it is in progress).  My only
obstacle is Canada's BDay weekend ;)

Here is a synopsis:  I'm going to disable input to the main window
through X or QT (I dont know how, but I'm sure there is a way), and then
take care of translation from input layer keycodes to QT events
(QApplication::postEvent) inside the plugin.  I'm working on the
configuration UI stuff right now.  The actual event device stuff is
easy.

Cheers!
-- 
Micah F. Galizia
mfgalizi at uwo.ca

"The mark of an immature man is that he wants to die
nobly for a cause, while the mark of the mature man is
that he wants to live humbly for one."   --W. Stekel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mythtv.org/pipermail/mythtv-dev/attachments/20050628/44a4ccf2/attachment.pgp