peter.hutterer at who-t.net
Thu Sep 4 02:26:24 PDT 2008
On Wed, Sep 03, 2008 at 11:02:12PM -0400, Chuck Robey wrote:
> I have it working, but since I had no least notion how to use those resolution
> parameters, and all of my attempts to get scaling to work by playing with those
> parameters failed, I used my own scaling transform immediately before I dispatch
> my events.
dont. set up the valuator ranges correctly and the server will scale to screen
coordinates for core events (Unless you're using some version of 1.4.0 which
had that particular bug).
> I have a bit more coding to do, I can see, I need to gen up an interface for the
> on-tablet function-key areas (detection. selection, and configuration). I have
> likewise total confusion about the Proximity ... I saw other drivers implement
> the events for it, though, so I did that too, but I don't see (onscreen) any
> effects from those events (I wouldn't recognize them if they work or not).
proximity events are a signal to clients that the device is - well, in
proximity. there is no visible effect unless a client decides to render one.
> I have only today figured out that you probably only want to dispatch valuator
> events if the Proximity is on, figured out because I used my tablet, and
> couldn't stand it without that. Maybe that'll become an option.
you don't dispatch valuator events. You dispatch pointer/proximity/key events,
and the server does the valuator events for you (if necessary). And of course,
only dispatch pointer events when you get data from the device.
More information about the xorg