From: Voluspa <li...@te...> - 2006-01-25 10:22:21
|
On Wed, 25 Jan 2006 10:43:48 +0100 Michael Kleiber wrote: > Hm - sorry for the trouble but as I wrote in my first post the XID of > the incoming events is the same no matter what device I use. Therefore > I thought I must do something fancy to differentiate the devices. > > As it now turns out I have to inspect the Proximity events as only > they deliver a valid XID to differentiate the input devices. I get > different IDs for cursor and stylus by looking at the Proximity > events. The DeviceMotionEvents on the other hand do always deliver > the same XID no matter what device I use (cursor, mouse, erasor). I > just thought it didn't matter what event I looked at to get the > correct deviceID. > > So, sorry again for the trouble but maybe you did not know that as > well? Ah yes, you did mention a "deviceid member" but my old eyes never recognized that as an XID. As for the Proximity event delivering the ID but Motion not, no I had no idea. That info could come in hand some day for me as well, one never knows. Xlib and XInput is a maze of dark corners. For example, pushing one of the buttons on the Intuos3 "pad" always triggers 1 Motion and 1 Button event (same with the release). So Motion in itself lacking ID might not be so strange after all - not even X really knows what it is for and to whom it belongs ;-) Mvh Mats Johannesson -- |