On Mon, Oct 24, 2011 at 04:02:46PM -0700, Ping Cheng wrote: > On Sun, Oct 23, 2011 at 8:22 PM, Peter Hutterer > <peter.hutte...@who-t.net> wrote: > >> > >> > what other axes are on this device? if it's just 2 anyway this is a > >> > nonissue. if there are other axes we need to rely on the client to > >> > determine > >> > which axis represents what anyway (already the case for XI 1.x) > >> > > >> > >> I haven't came up to speed on application side or if server can handle > >> wholes in valuator lists and why I haven't submitted anything yet. I > > > > XI2 handles it on the protocol side,, the server should be able to handle it > > nowadays too though that code has not seen much exposure yet. note that to > > use this in the wacom driver would mean either ifdef hell or dropping > > support for older server versions since currently we're still using the old > > input apis. > > I know you don't like ifdefs (me neither). But I don't feel we can > afford either dropping support for older servers or maintaining more > than one xf86-input-wacom branch. I am waiting for the day that I can > drop linuxwacom for good.
how many users of X servers 1.7-1.11 do you have that cannot possibly update? > Hope someone can save us from this "hell" ;). unlikely to happen. The better course of action is to define which server versions are supported for long and maintain those (as we do with RHEL). I've been doing backwards-compat code for wacom because it didn't hold anything back (much). As soon as the driver is held back by having support for a server generation from 2 years ago, I'll happily drop that support. > >> 1) My device advertises Pressure support with range of 0-4096 but > >> never sends anything. If I was an application writer (I'm not, BTW, > >> so could be wrong :-) ), I would make assumptions when I saw that > >> valuator declared. I'd stop looking for left click and instead start > >> looking for some non-zero pressure value as left click. > > > > that sounds like a kernel bug. the device shouldn't advertise the axis > > if it doesn't use it (possibly quirked out if the HW is at fault) > > It is not a kernel driver issue. It is an issue in wcmInitAxes > (xf86Wacom.c). We did not check if the axis is defined or not before > calling InitValuatorAxisStruct. oh. so it's not the kernel that advertises the pressure axis then? in that case, we should be able to fix it "easily" Cheers, Peter ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
