> > I think the bottom line is that even if the "directness" of a device > > is configurable, it still needs to have a default. Moreover, the > > notion of kernel mode settings could be applicable here too. > > Talking about default mode, there are cases that the mode is decided > by the tools running on the device/tablet, instead of the tablet > itself. > > Take Wacom's Intuos and Graphire series for example, those tablets > support both styli and mice. For styli, the default is absolute mode; > while for mice, it is relative. So, only valid property the tablet can > tell the user-land is: I am a tablet, i.e., not a touchscreen. Clients > have to check the tool types to set the default mode to relative > (BTN_TOOL_MOUSE/LENS) or absolute (BTN_TOOL_PEN/AIRBRUSH/RUBBER...). And those modes can be determined using the available axes. However, when all axes are the same, a statement like "I am a tablet" does not exist. In that case, distinguishing between touchscreen, touchpad and tablet becomes a question of interpreting the properties. Such a distinction cannot be achieved using a single bit of information, and that was never the intention. In short: I think Chris' comments are spot on, and incorporating them into the patch would be good to avoid further confusion. Thanks, Henrik -- 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
