On Sat, Aug 24, 2013 at 4:50 PM, Dmitry Torokhov <dmitry.torok...@gmail.com> wrote: > > Hi Jason, > > On Thu, Aug 22, 2013 at 06:15:36PM -0700, Jason Gerecke wrote: > > Android marks found axes as 'valid' only if they have a minimum > > and maximum value that aren't equal. Since we don't actually > > assign any range information for ABS_MISC, Android doesn't bother > > to mark it such. This prevents userspace from being able to make > > use of tool serial information. > > That should be fixed in Android code. Min/max are filled on best effort > basis and 0/0 is effectively unknown. > > Thanks. > > -- > Dmitry
If userspace is written with the assumption that 0/0 == unknown, then this patch changes nothing since the consumer will expect any value between INT_MIN and INT_MAX anyway. Furthermore, if some userspace program strictly interprets 0/0 to mean "will always be equal to 0", then this patch actually provides it with the correct range. Either way, setting the values to INT_MIN and INT_MAX does nothing more than explicitly state the correct range. I agree that Google should re-visit the function which does this "valid" filtering, but I don't see a problem with this patch. Jason --- Now instead of four in the eights place / you’ve got three, ‘Cause you added one / (That is to say, eight) to the two, / But you can’t take seven from three, / So you look at the sixty-fours.... ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
