Hi, On Wed, 2009-05-06 at 23:54 +0300, Ville Syrjälä wrote:
> An input driver can implement the GetAxisInfo() method which the input > core then can use to get the min/max values during init. It will then > fill the min/max in an axis abs event with those values unless they > were already set. Oh, I didn't realize that. That makes it a lot easier to fix this. Thanks for pointing out this detail. > With linux_input it's at least theoretically possible that the min/max > values can change during the lifetime of the device so I'm not sure if > GetAxisInfo() would be the best option. On the other hand there doesn't > seem to be any event sent when those parameters change so users of the > device wouldn't notice the change anyway unless they actively poll the > device. Maybe EV_SYN/SYN_CONFIG was meant for that but at least I can't > see any use of that event in the kernel source. Is that a theoretical possibility or are there actually devices that make use of this? IMO it would be better to provide the min/max values with the very small risk of them becoming incorrect than not to provide them at all. I will try to implement GetAxisInfo() in the linux-input driver then. Sven _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
