On Wed, 18 Jan 2006, Darren Salt wrote:
> I demand that J.O. Aho may or may not have written...
>
> [snip]
>> For the hauppauge_new the following keys don't generate anything in xev
>> KEY_RED
>> KEY_GREEN
>> KEY_BLUE
>> KEY_YELLOW
>> KEY_CHANNELUP
>> KEY_CHANNELDOWN
>> KEY_ZOOM
>> KEY_SELECT (shouldn't the 0x3b have been mapped to KEY_GO ?)
>> KEY_RADIO
>
> Same here. I think that X doesn't have appropriate mappings for them.
>
> KEY_SELECT is an established mapping, so I'd leave it as it is; I'd only
> change it if the entire keymap was inappropriate. However, you *should* be
> able to change it with input-kbd (part of input-utils).
>
> (And I see no KEY_GO; do you mean KEY_GOTO?)
I'm quite sure I have seen KEY_GO, but can't locate it at all today, it's
closer to two years go I looked into what options was for keys, could also
be that I may have mixed it with XF86Go form XKeysymDB.
>> If thise had generated results, then you could skipp the usage of lircd as
>> you could have those keyboard shortcuts.
>
> OTOH, it becomes a matter of input focus. With lircd or some other program
> which directly opens the appropriate input device node, that doesn't matter.
I have run into the problem that having two or more tools open that is
handled by lircd, they all are affected by key pressed on the remote, but
maybe there are ways to control this in the settings and really don't
belong in this maillist, but it had been good if all keys had been
"valid", so each user could choose how they want to have things. As I have
some "none valid" keys on my multimedia keyboard, I guss this is kind of
a X issue.
--
//Aho
------------------------------------------------------------------------
E-Mail: trizt@xxxxxxxxx URL: http://www.kotiaho.net/~trizt/
ICQ: 13696780
System: Linux System (PPC7447/1000 AMD K7A/2000)
------------------------------------------------------------------------
EU forbids you to send spam without my permission
------------------------------------------------------------------------
