Hi, On Tue, Nov 23, 2010 at 04:07:20PM +1000, Peter Hutterer wrote: > On Fri, Nov 19, 2010 at 01:52:39PM -0500, Chase Douglas wrote: > > A touch event is not delivered according to the device hierarchy. All touch > > -events are sent only through their originating slave devices. > > +events are sent only through their originating slave devices. However, > > +dependent touch devices will only emit touch events if they are attached > > to a > > +master device. This is due to the touch delivery being dependent on the > > +location of a cursor. > > it is still not clear why you don't want to route touch events through the > master device (other than that leaving it in the SD alone is easier to > implement). is there a list of pros and cons for both approaches? > > especially in the case of touch-based pointer emulation, when the master > will send events caused by the slave device. so some events have to be > routed either way.
The best reason I can think of is that requiring clients to track hierachy events and (de)select events manually for every single device is lame, as well as inherently racy. Cheers, Daniel
signature.asc
Description: Digital signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
