Stumped with STopX0 being set wrong...

View: New views
3 Messages — Rating Filter:   Alert me  

Stumped with STopX0 being set wrong...

by Kelly Price :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Okay, I have Gentoo amd64 (64-bit mode) just freshly compiled up
today, Xorg server 1.6 running on an NVidia Geforce 8600.  Just
compiled up the latest version, set ScreenNo in my xorg.config to "0"
to force it to my larger main screen (a 1920x1200 LCD, :0.0). The
screen to the left of that is a 1680x1050 LCD, :0.1.  I'm not running
Xinenama nor TwinView, although R-and-R  is screwing the window layout
because it thinks that it has extra space under screen :0.1 where I
can't see it in real life.

Enough of that rambling; the problem is that that the Wacom's only
using the right half of screen :0.0.

Here's a listing of all the parameters.  As you can see, STopX0's set
to 1680.  Shouldn't that be "0"?
tygris@redwolf ~ $ xsetwacom list param | perl -nle
'if(/^(\S+)\s+-/){$z=$1;$b=`xsetwacom get stylus $z`; chomp $b; print
"$z: $b";}'

TopX: 0
TopY: 0
BottomX: 16704
BottomY: 12064
Button1: 1
Button2: 2
Button3: 3
Button4: 4
Button5: 5
Button6: 6
Button7: 2
Button8: 2
Button9: 2
Button10: 2
Button11: 2
Button12: 2
Button13: 2
Button14: 2
Button15: 2
Button16: 2
Button17: 2
Button18: 2
Button19: 2
Button20: 2
Button21: 2
Button22: 2
Button23: 2
Button24: 2
Button25: 2
Button26: 2
Button27: 2
Button28: 2
Button29: 2
Button30: 2
Button31: 2
Button32: 2
DebugLevel: 0
CommonDBG: 0
Suppress: 2
RawSample: 4
Screen_No: 0
PressCurve: 25700
TwinView: 0
Mode: 1
TPCButton: 0
Touch: 0
Capacity: -1
CursorProx: -1
Rotate: 0
RelWUp: 5
RelWDn: 4
AbsWUp: 0
AbsWDn: 0
StripLUp: 4
StripLDn: 5
StripRUp: 4
StripRDn: 5
TVResolution0: -1
TVResolution1: -1
RawFilter: 1
SpeedLevel: 6
ClickForce: 5
Threshold: 30
Accel: 1
xyDefault: -1
mmonitor: 1
CoreEvent: 1
STopX0: 1680
STopY0: 0
SBottomX0: 3600
SBottomY0: 1200
STopX1: 0
STopY1: 0
SBottomX1: 1680
SBottomY1: 1050
STopX2: -1
STopY2: -1
SBottomX2: -1
SBottomY2: -1
STopX3: -1
STopY3: -1
SBottomX3: -1
SBottomY3: -1
STopX4: -1
STopY4: -1
SBottomX4: -1
SBottomY4: -1
STopX5: -1
STopY5: -1
SBottomX5: -1
SBottomY5: -1
STopX6: -1
STopY6: -1
SBottomX6: -1
SBottomY6: -1
STopX7: -1
STopY7: -1
SBottomX7: -1
SBottomY7: -1
ToolID: 2
ToolSerial: 0
Serial: 0
TabletID: 22
GetTabletID: 22
NumScreen: 2
XScaling: 0



--
Kelly "STrRedWolf" Price
http://strredwolf.furrynet.com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Stumped with STopX0 being set wrong...

by Ping@LinuxWacom :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

That output tells me you have a dual monitor setup similar to the"LeftOf" setup of Xinenama or TwinView, i.e. the first monitor (screen 0) is on the left.  Can you trace into the code to see what got confused there?  It should be somewhere in wcmCommon.c or xf86Wacom.c. 

Ping

On Mon, Oct 12, 2009 at 3:36 PM, Kelly Price <strredwolf@...> wrote:
Okay, I have Gentoo amd64 (64-bit mode) just freshly compiled up
today, Xorg server 1.6 running on an NVidia Geforce 8600.  Just
compiled up the latest version, set ScreenNo in my xorg.config to "0"
to force it to my larger main screen (a 1920x1200 LCD, :0.0). The
screen to the left of that is a 1680x1050 LCD, :0.1.  I'm not running
Xinenama nor TwinView, although R-and-R  is screwing the window layout
because it thinks that it has extra space under screen :0.1 where I
can't see it in real life.

Enough of that rambling; the problem is that that the Wacom's only
using the right half of screen :0.0.

Here's a listing of all the parameters.  As you can see, STopX0's set
to 1680.  Shouldn't that be "0"?
tygris@redwolf ~ $ xsetwacom list param | perl -nle
'if(/^(\S+)\s+-/){$z=$1;$b=`xsetwacom get stylus $z`; chomp $b; print
"$z: $b";}'

TopX: 0
TopY: 0
BottomX: 16704
BottomY: 12064
Button1: 1
Button2: 2
Button3: 3
Button4: 4
Button5: 5
Button6: 6
Button7: 2
Button8: 2
Button9: 2
Button10: 2
Button11: 2
Button12: 2
Button13: 2
Button14: 2
Button15: 2
Button16: 2
Button17: 2
Button18: 2
Button19: 2
Button20: 2
Button21: 2
Button22: 2
Button23: 2
Button24: 2
Button25: 2
Button26: 2
Button27: 2
Button28: 2
Button29: 2
Button30: 2
Button31: 2
Button32: 2
DebugLevel: 0
CommonDBG: 0
Suppress: 2
RawSample: 4
Screen_No: 0
PressCurve: 25700
TwinView: 0
Mode: 1
TPCButton: 0
Touch: 0
Capacity: -1
CursorProx: -1
Rotate: 0
RelWUp: 5
RelWDn: 4
AbsWUp: 0
AbsWDn: 0
StripLUp: 4
StripLDn: 5
StripRUp: 4
StripRDn: 5
TVResolution0: -1
TVResolution1: -1
RawFilter: 1
SpeedLevel: 6
ClickForce: 5
Threshold: 30
Accel: 1
xyDefault: -1
mmonitor: 1
CoreEvent: 1
STopX0: 1680
STopY0: 0
SBottomX0: 3600
SBottomY0: 1200
STopX1: 0
STopY1: 0
SBottomX1: 1680
SBottomY1: 1050
STopX2: -1
STopY2: -1
SBottomX2: -1
SBottomY2: -1
STopX3: -1
STopY3: -1
SBottomX3: -1
SBottomY3: -1
STopX4: -1
STopY4: -1
SBottomX4: -1
SBottomY4: -1
STopX5: -1
STopY5: -1
SBottomX5: -1
SBottomY5: -1
STopX6: -1
STopY6: -1
SBottomX6: -1
SBottomY6: -1
STopX7: -1
STopY7: -1
SBottomX7: -1
SBottomY7: -1
ToolID: 2
ToolSerial: 0
Serial: 0
TabletID: 22
GetTabletID: 22
NumScreen: 2
XScaling: 0



--
Kelly "STrRedWolf" Price
http://strredwolf.furrynet.com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Stumped with STopX0 being set wrong...

by Kelly Price :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Actually, the first monitor was to the right of the second one, but
the /etc/X11/xorg.conf file was misconfigured by NVidia's tool.  Turns
out, it configured screen 0 to be 1680 pixels to the right in the
Screen entry under the ServerLayout section.  Resetting it to "0 0"
fixed the problem.

On Wed, Oct 14, 2009 at 6:16 PM, Ping <pinglinux@...> wrote:

> That output tells me you have a dual monitor setup similar to the"LeftOf"
> setup of Xinenama or TwinView, i.e. the first monitor (screen 0) is on the
> left.  Can you trace into the code to see what got confused there?  It
> should be somewhere in wcmCommon.c or xf86Wacom.c.
>
> Ping
>
> On Mon, Oct 12, 2009 at 3:36 PM, Kelly Price <strredwolf@...> wrote:
>>
>> Okay, I have Gentoo amd64 (64-bit mode) just freshly compiled up
>> today, Xorg server 1.6 running on an NVidia Geforce 8600.  Just
>> compiled up the latest version, set ScreenNo in my xorg.config to "0"
>> to force it to my larger main screen (a 1920x1200 LCD, :0.0). The
>> screen to the left of that is a 1680x1050 LCD, :0.1.  I'm not running
>> Xinenama nor TwinView, although R-and-R  is screwing the window layout
>> because it thinks that it has extra space under screen :0.1 where I
>> can't see it in real life.
>>
>> Enough of that rambling; the problem is that that the Wacom's only
>> using the right half of screen :0.0.
>>
>> Here's a listing of all the parameters.  As you can see, STopX0's set
>> to 1680.  Shouldn't that be "0"?
>> tygris@redwolf ~ $ xsetwacom list param | perl -nle
>> 'if(/^(\S+)\s+-/){$z=$1;$b=`xsetwacom get stylus $z`; chomp $b; print
>> "$z: $b";}'
>>
>> TopX: 0
>> TopY: 0
>> BottomX: 16704
>> BottomY: 12064
>> Button1: 1
>> Button2: 2
>> Button3: 3
>> Button4: 4
>> Button5: 5
>> Button6: 6
>> Button7: 2
>> Button8: 2
>> Button9: 2
>> Button10: 2
>> Button11: 2
>> Button12: 2
>> Button13: 2
>> Button14: 2
>> Button15: 2
>> Button16: 2
>> Button17: 2
>> Button18: 2
>> Button19: 2
>> Button20: 2
>> Button21: 2
>> Button22: 2
>> Button23: 2
>> Button24: 2
>> Button25: 2
>> Button26: 2
>> Button27: 2
>> Button28: 2
>> Button29: 2
>> Button30: 2
>> Button31: 2
>> Button32: 2
>> DebugLevel: 0
>> CommonDBG: 0
>> Suppress: 2
>> RawSample: 4
>> Screen_No: 0
>> PressCurve: 25700
>> TwinView: 0
>> Mode: 1
>> TPCButton: 0
>> Touch: 0
>> Capacity: -1
>> CursorProx: -1
>> Rotate: 0
>> RelWUp: 5
>> RelWDn: 4
>> AbsWUp: 0
>> AbsWDn: 0
>> StripLUp: 4
>> StripLDn: 5
>> StripRUp: 4
>> StripRDn: 5
>> TVResolution0: -1
>> TVResolution1: -1
>> RawFilter: 1
>> SpeedLevel: 6
>> ClickForce: 5
>> Threshold: 30
>> Accel: 1
>> xyDefault: -1
>> mmonitor: 1
>> CoreEvent: 1
>> STopX0: 1680
>> STopY0: 0
>> SBottomX0: 3600
>> SBottomY0: 1200
>> STopX1: 0
>> STopY1: 0
>> SBottomX1: 1680
>> SBottomY1: 1050
>> STopX2: -1
>> STopY2: -1
>> SBottomX2: -1
>> SBottomY2: -1
>> STopX3: -1
>> STopY3: -1
>> SBottomX3: -1
>> SBottomY3: -1
>> STopX4: -1
>> STopY4: -1
>> SBottomX4: -1
>> SBottomY4: -1
>> STopX5: -1
>> STopY5: -1
>> SBottomX5: -1
>> SBottomY5: -1
>> STopX6: -1
>> STopY6: -1
>> SBottomX6: -1
>> SBottomY6: -1
>> STopX7: -1
>> STopY7: -1
>> SBottomX7: -1
>> SBottomY7: -1
>> ToolID: 2
>> ToolSerial: 0
>> Serial: 0
>> TabletID: 22
>> GetTabletID: 22
>> NumScreen: 2
>> XScaling: 0
>>
>>
>>
>> --
>> Kelly "STrRedWolf" Price
>> http://strredwolf.furrynet.com
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Linuxwacom-discuss mailing list
>> Linuxwacom-discuss@...
>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>
>



--
Kelly "STrRedWolf" Price
http://strredwolf.furrynet.com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss