On Fri, May 06, 2011 at 10:23:48AM +1000, Peter Hutterer wrote: > On Fri, May 06, 2011 at 01:06:41AM +0100, Daniel Stone wrote: > > On Fri, May 06, 2011 at 09:16:38AM +1000, Peter Hutterer wrote: > > > On Thu, May 05, 2011 at 09:35:52AM +0200, Cedric Sodhi wrote: > > > > 2.) Would you consider including an option which turns the touchpad off > > > > on keyboard (or other) input into the driver - so that ones doesnt > > > > requie a helper program for that? > > > > > > no, the driver doesn't know when keyboard input is made. and given that > > > any > > > such option will soon want about 15 configuration options, it's better to > > > keep it in a client program. > > > > Eh, it's actually easily doable; just have a per-device property for the > > time in millis to ignore all input for after a keyboard event, and do it > > all in DIX if that property is ever set on a device. > > > > That way you can still have the clients in control, but you don't have > > to rely on an external daemon constantly enabling and disabling your > > touchpad. > > do you want to enable/disable based on modifiers too?
No. Why would you? > only modifiers, but combos as well (ctrl+c, ctrl+v)? As above. > do you want to only disable tapping/scrolling, but not movement? No. > seriously, the options will just pile up, requiring configuration, etc. and > the last thing we need is more config options and properties. I agree, but we don't have to add them. Cheers, Daniel _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
