On Thu, May 31, 2012 at 08:02:18PM +0200, Cedric Sodhi wrote: > Hello, > > now there ais all kind of multiness involved with wacom, > > Multitouch (as in, well, multitouch), > > Multiple Pointers (as in, one or more pointers from the touchscreen, > others from the digizizer, ...) > > Multiple Devices (as in, touchscreen, digitizer, yet another > touchscreen, ...) > > all of which become increasingly important. I'm particularly affected > because my computer, a tablet by the name of "EEE Slate" consists of the > following two devices > > * A Wacom ISDV4 Digitizer > * An EETI eGalax Touchscreen, also powered by the Wacom driver (thanks > to Chris and Ben Tissoires from linux-input at this point again, without > whom I'd not have gotten this to work in the first place) > > Which it is of course not the canonical case, one may equally imagine > the same situation with the eGalax replaced by some Wacom touchscreen. > > For my personal case, I've solved the dilemma of the touchscreen and the > wacom fighting with eachother by adding some rather ugly hacks to the X > driver, none of which is sustainable or desirable in the long run. > > There is still the multitouch issue - with the newest X.org and evdev I > could use multitouch, indeed, and thereby abandon wacom. > > Long story short: > > How are things to proceed from here. Is there a master plan which > rectifies all the three issues at once and provides one consistent > solution for arbitrary configurations, and also incorporates multitouch > and multipointer? > > I know the whole issue spreads through all layers of the input-world, > from the x-driver, to the kernel level. > > I guess people like Peter have the ultimate overview of the whole > sitation. I'd like to contribute, preferably at the X driver layer, but > the current situation is very unclear to me - I don't even want to think > of wayland, which just makes the future possibilities even less > transparent. > > Could you sum up the whole situation in a few short sentences and > outline which responsibility goes where and which issues have already > been solved or subjected to a plan which is meant to solve them? > > To sum up, what's the situation of and relation among > > MPX <-> > Multitouch <-> > Precedence and MPX/Multitouch accross multiple, > inherently unrelated (arbitrary) devices > > in wacom and linux input in general?
MPX and multitouch are orthogonal and neither affects the other. You can have multiple MPX master devices that support multitouch. Within the wacom driver we have code to ignore touch if pen input is active, but this code doesn't trigger if the devices are driven by different drivers. I don't really have a good answer here, the input drivers are too isolated from each other to do anything in the driver, so what we'll need is most likely some client-side support thing, similar to syndaemon. not impossible but tricky, though it should be easier with the new per-device idletime counters. Cheers, Peter ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
