Keymap issues with Pointer+Keys device

[Sascha Hlusiak]

> > Here, "panic" set to TRUE doesn't seem so right but it's the only way I
> > found to totally remove a device.
>
> Sounds alright. The panic is necessary as you can't call RemoveDevice
> directly (which would disable everything properly).
Great, thank you.


> I'm thinking, maybe it might be worth making NewInputDeviceRequest and
> DeleteInputDeviceRequest part of the server API. That way, you could just
> assemble the option list, pass it in and let the server worry about the
> rest.
Yes, I was looking for methods like this to call. While what I do already is a 
workaround for Pointer+Key devices, it would be much cleaner for now to have 
an API for creating devices out of a driver. The evdev driver has the same 
issue, if there are keyboards with valuators.

BTW: With MPX, having two key devices attached to the first master device 
works fine, regarding the keymap. When creating a second master and attaching 
a keyboard to that, key presses seem to use the keymap of the first master 
device, so of the other keyboard.


Cheers,
Sascha
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.x.org/archives/xorg/attachments/20080916/843c5175/attachment.pgp>