On Mon, Mar 7, 2011 at 2:19 PM, Peter Hutterer <[email protected]>wrote:
> On Mon, Mar 07, 2011 at 01:38:58PM -0600, Favux ... wrote:
> > Hi Peter,
> >
> > Made the suggested changes.
> >
> > Favux
>
> > From aafa3b221888cc8c97b244010842cbaa96ac5951 Mon Sep 17 00:00:00 2001
> > From: David <[email protected]>
> > Date: Mon, 7 Mar 2011 12:56:35 -0600
> > Subject: [Patch v2 1/1] xsetwacom.man: Add 5 parameters
> >
> > Add Mode, PressureCurve, Rotate, TabletPCButton, and Threshold. And
> other changes.
> >
> > Signed-off-by: David Foley <[email protected]>
> > ---
> > man/xsetwacom.man | 66
> ++++++++++++++++++++++++++++++++++++++++++++---------
> > 1 files changed, 55 insertions(+), 11 deletions(-)
> >
> > diff --git a/man/xsetwacom.man b/man/xsetwacom.man
> > index 67f8439..05e3450 100644
> > --- a/man/xsetwacom.man
> > +++ b/man/xsetwacom.man
> > @@ -66,7 +66,8 @@ Get the current settings for the parameter on the given
> device. Note that
> > not all parameters are available on all device types. The special
> parameter
> > name "all" may be provided to display all current settings on the
> device.
> > .TP
> > -By default, options are printed on the commandline in the respective
> format. The output format may be altered with one of the following options:
> > +By default, options are printed on the commandline in the respective
> format.
> > +The output format may be altered with one of the following options:
> > .TP
> > \fB-s, --shell\fR
> > Display the output in shell format, i.e. as shell commands to xsetwacom
> to
> > @@ -84,16 +85,20 @@ not all parameters are writable, some are read-only
> and result in an error
> > when trying to be modified.
> >
> > .SH "PARAMETERS"
> > +.LP
> > +Not all parameters are available on all tools. Use the get command with
> the
> > +parameter or "all" parameter for specific input tool applicable
> parameters
> > +and current settings.
> > .TP
> > \fBArea\fR x1 y1 x2 y2
> > -Specify the tablet input area in device coordinates in the form top left
> > +Set the tablet input area in device coordinates in the form top left
> > x/y and bottom right x/y. Top left and bottom right are defined in the
> > device's native orientation, regardless of the actual rotation currently
> > -applied. Input outside of these coordinates will be clipped
> > -to the edges of the area defined.
> > +applied. Input outside of these coordinates will be clipped to the edges
> > +of the area defined. Default: 0 0 x2 y2; with x2 and y2 tablet
> specific.
>
> btw, technically this is is a bug that just happens to not show up because
> all tablets have 0/0 maxx/maxy. I've got patch in the pipe to undo the 0/0
> requirement but not sure how to test this.
>
It can be tested by the following set up:
Make topX = -500 and leave all the other values unchanged. If the mapping
code works properly, you'll see a strip along the left edge of your screen
where you do not see cursor movement. That is, when we start from the left
edge of the tablet, the cursor is mapped starting from an X value, call it
sTopX for now, that is larger than 0 instead of 0. This happens because, in
theory, the tablet area from x = -500 to 0 is mapped to screen area from x =
0 to sTopX. Since tablet does not post negative (x,y), we can not reach the
area from 0 to TopX on the screen.
That is how the calibration works for display tablet.
Ping
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
