Keymap issues with Pointer+Keys device

[Peter Hutterer]

On Tue, Sep 23, 2008 at 08:36:13PM +0200, Sascha Hlusiak wrote:
> > Note that if you're using core clients, this is "intended" behaviour.
> > Remember that the ClientPointer (CP) always assigns a "primary" master
> > device to a core client.
> >
> > So the call order is something like:
> > Client requests keymap, server replies with CP's keymap.
> > If you then hit a key on kbd 2, the server notifies the client that the
> > keymap has changed.
> > Client requests keymap, server replies with CP's keymap.
> >
> > oops.
> >
> > solution: fix the client :)
> So, is xev 'broken' then?

yes, because it has to follow the same procedure. Only clients that use
XGetDeviceKeymapping instead of XGetKeyboardMapping can work properly.

Cheers,
  Peter