Hi Vojtech, I have a question about the "contract" of the evdev interface...
I have 2 touch screens, both USB. Both of them have drivers (hid-input and mtouchusb) that provide ABS_X and ABS_Y coordinates to the input subsystem and so I read those coordinates from userspace. However, one of the touch screens (ELO, via hid-input) reports coordinates with the origin in the upper-left corner, i.e. touching the upper-left corner of the screen reports 0,0. The other touch screen (3M, via mtouchusb) reports coordinates with the origin at the bottom-left corner. So my question is, can an evdev app assume a specific origin? Normal screen origin, i.e. upper-left, would make the most sense to me. If so, it seems that mtouchusb should flip its Y coordinates before sending to the input subsystem (which would be an easy patch of course). Or, can an app not rely on evdev's coordinate origin being upper-left? Thanks! -- Dan Streetman [EMAIL PROTECTED] --------------------- 186,272 miles per second: It isn't just a good idea, it's the law! ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
