With this regard, I am a big fan of the idea of having hierarchical
devices, just like with have hierarchical file systems. Each finger
on the dual-touch panel would be a device, child of the panel
device. Each would be equivalent to a mouse, and voila, the symmetry
is restored. Conceptually, saying (panel/finger1, any event) or
(panel, finger1 events) are equivalent; but in the first case the
routing is done by the OS and in the second case it has to be done
by the app, which breaks reusability. There are other interesting
perspectives, but I don't want to get carried away too much.
Theoretically it is nice but it practice the cases are differemt: with
mice you are dealing with 2 separate devices whereas with touchscreen
there is one and it is mater of interpretation whether 2 touches should
be taken as independent events or a complex gestures.
I see your point, reporting the position on separate axes (ABS_X and
ABS_MT_X) isn't as problematic as seeing TOUCH turn on twice.
--
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
