On Tue, May 25, 2010 at 09:52:29PM +0200, Henrik Rydberg wrote: > Dmitry Torokhov wrote: > > Hi Henrik, > > > > On Tue, May 25, 2010 at 01:52:57PM +0200, Henrik Rydberg wrote: > >> These patches are in response to the discussion about input state > >> retrieval. > >> > >> The current EVIOCGABS method does not work with MT slots. These > >> patches provides a mechanism where a slot is first selected via a call > >> to EVIOCSABS, after which the corresponding MT events can be extracted > >> with calls to EVIOCGABS. > >> > >> The symmetric operation, to set the MT state via EVIOCSABS, seems to > >> violate input data integrity, and is therefore not implemented. > >> > > > > This looks sane, however the question remains - is there any users for > > this data? Like I mentioned, I can see the need to fetch state of > > switches and ranges of absolute axis, and even non-multitouch ABS values > > (due to the fact that some input devices, like sliders, may stay in a > > certain position for long periods of time), but I expect multitouch data > > to be "refreshed" very quickly. > > > > Thanks. > > > > There were some voices addressing this issue, and the patches are here, > available for whomever to pick up. Drop them if you wish, I will not send them anew. > I'll save them in my queue but will hold off applying until I hear userspace folks requesting such functionality. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
