On Mon, Dec 13, 2010 at 05:51:25PM -0800, Ping Cheng wrote:
> On Mon, Dec 13, 2010 at 5:05 PM, Peter Hutterer
> <[email protected]> wrote:
> > On Mon, Dec 13, 2010 at 12:03:59PM -0800, Ping Cheng wrote:
> >> On Sun, Dec 12, 2010 at 7:30 PM, Peter Hutterer
> >> <[email protected]> wrote:
> >> > The pad doesn't actually send events on the third axis, it simply acts 
> >> > as a
> >> > filler so that client's don't misinterpret the actual axis the device 
> >> > has.
> >>
> >> Then what about the first and second axes? Pad does not send x and y
> >> events either. Shouldn't we add the filter for x and y as well?
> >
> > x/y are special, because I don't think any client or device can afford to
> > have axes 0 and 1 as something other than x/y.
> 
> I see your point. But, is there a consistent way to tell the client
> that an axis is not going to post any events? In addition to the
> pressure is not just supported, the third axis does not report any
> events at all. Neither the first nor the second.

no. you could argue that if we _know_ that an axis isn't sending events
anwyay, there is little point of initializing it in the first place...
(I know, backwards compat with clients, etc.)

> > other axes are different, the labels are there to tell a client what axis
> > this could stand for. what this commit is trying to avoid is that potential
> > UIs claim that the pad supports pressure (based on the axis label) when it
> > doesn't.
> 
> Pad does not support x and y either.

at this point, every device needs x/y to function properly with the clients
that we have.

> >> > Initialize it as relative axis, because the rest of the pad is relative 
> >> > too.
> >>
> >> Well, depends on which "rest" we are refering to. The fouth to sixth
> >> valuators are all in absolute mode.
> >
> > the pad itself is relative (and forced relative too). I'll likely change
> > this back to absolute (I think it used to be absolute and got changed due to
> > a server bug)
> 
> It used to be in absolute mode if it is not a core device; in relative
> mode if it is a core device. But forced to relative mode since the
> removal of core/non-core concept in the server.

ah. good old XI1 and the core concept...
I think we can switch it back to absolute, the server should be fixed. needs
some more testing though.

Cheers,
  Peter

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to