On Tue, May 05, 2009 at 09:33:29AM +0200, Gregory Smirnov wrote:
> 2009/5/4 Alan Coopersmith
> > Your program has always been broken then - X keycodes are different
> > on different platforms and servers, and as kbd/evdev show, sometimes
> > even different drivers on the same server/platform. It
2009/5/4 Alan Coopersmith
> Gregory Smirnov wrote:
> > Hello, I use program that depends on X keycodes as well and have the
> > same problem.
>
> Your program has always been broken then - X keycodes are different
> on different platforms and servers, and as kbd/evdev show, sometimes
> even diffe
Gregory Smirnov wrote:
> Hello, I use program that depends on X keycodes as well and have the
> same problem.
Your program has always been broken then - X keycodes are different
on different platforms and servers, and as kbd/evdev show, sometimes
even different drivers on the same server/platform.
On Mon, May 04, 2009 at 11:09:31AM +0200, Gregory Smirnov wrote:
> 2009/5/3 Matthew Garrett
>
> > On Sun, May 03, 2009 at 08:00:28PM +0200, Marvin Raaijmakers wrote:
> > > Yes I know the kernel keycode to X keycode translation is fixed for
> > > each keyboard driver. But the problem is that the e
2009/5/3 Matthew Garrett
> On Sun, May 03, 2009 at 08:00:28PM +0200, Marvin Raaijmakers wrote:
> > Yes I know the kernel keycode to X keycode translation is fixed for
> > each keyboard driver. But the problem is that the evdev driver (in the
> > X server) does another translation than the kbd dri
On Sun, May 03, 2009 at 08:00:28PM +0200, Marvin Raaijmakers wrote:
> Yes I know the kernel keycode to X keycode translation is fixed for
> each keyboard driver. But the problem is that the evdev driver (in the
> X server) does another translation than the kbd driver. You stated:
> "As long as the
Yes I know the kernel keycode to X keycode translation is fixed for
each keyboard driver. But the problem is that the evdev driver (in the
X server) does another translation than the kbd driver. You stated:
"As long as the kernel keycode is KEY_BATTERY, the X keycode will
depend only on whether kb
On Thu, Apr 30, 2009 at 07:20:13PM +0100, Matthew Garrett wrote:
> On Thu, Apr 30, 2009 at 08:09:01PM +0200, Marvin Raaijmakers wrote:
> > Well a scancode is for the kernel like what a X keycode is to the X
> > server, and a kernel keycode is for the kernel what a key symbol is to
> > the X server.
On Thu, Apr 30, 2009 at 08:09:01PM +0200, Marvin Raaijmakers wrote:
> Well a scancode is for the kernel like what a X keycode is to the X
> server, and a kernel keycode is for the kernel what a key symbol is to
> the X server. So when you change the kernel keycode of a key, then the
> X server will
Well a scancode is for the kernel like what a X keycode is to the X
server, and a kernel keycode is for the kernel what a key symbol is to
the X server. So when you change the kernel keycode of a key, then the
X server will receive another kernel keycode from the kernel and as a
result the key will
On Tue, Apr 28, 2009 at 11:10:57AM +0200, Marvin Raaijmakers wrote:
> Well I developed keyTouch, a program that allows the user to bind
> actions to extra function keys (like the Play/Pause, WWW or Zoom keys
> for example) on a keyboard. KeyTouch is a collection of programs. One
> program binds a k
The XClient is not doing the wrong thing. I am not talking about an X
keycode to X key symbol binding. The first program changes the kernel
keycode (so not the X keycode), that is bound by the keyboard driver
inside the kernel, to the scancode of a key. The when a key is
pressed, the kernel driver
On Tue, Apr 28, 2009 at 11:10:57AM +0200, Marvin Raaijmakers wrote:
> Well I developed keyTouch, a program that allows the user to bind
> actions to extra function keys (like the Play/Pause, WWW or Zoom keys
> for example) on a keyboard. KeyTouch is a collection of programs. One
> program binds a k
Well I developed keyTouch, a program that allows the user to bind
actions to extra function keys (like the Play/Pause, WWW or Zoom keys
for example) on a keyboard. KeyTouch is a collection of programs. One
program binds a key's scancode to a Linux keycode. So it changes the
mapping inside the Linux
On Mon, Apr 27, 2009 at 09:15:22PM +0200, Marvin Raaijmakers wrote:
> Is there a way to detect, from the host that runs the X clients, what
> keyboard driver is used by the X server? I want to know this because I
> want to write a program that should behave differently when the evdev
> driver is us
Is there a way to detect, from the host that runs the X clients, what
keyboard driver is used by the X server? I want to know this because I
want to write a program that should behave differently when the evdev
driver is used instead of the traditional keyboard driver.
Regards,
Marvin Raaijmakers
16 matches
Mail list logo
