Nabble - linuxwacom-discuss

Re: no calibrate button on wacomcpl

2009-12-01T15:37:32Z

Ok, got wacomcpl to give me the calibrate option.

by changing the wacomcpl-exec script so that the variable $calibrate is
true. However, can't work out why its false in the first place.

On Sun, 2009-11-29 at 10:32 -0800, Png wrote:

> Hi Richard,
>
> I think you've got "something nice" before Christmas - a working
> driver from Wacom and the linuxWacom community. It would be a time
> for you to bring something back to us in January :).
>
> Ping
>
> P.S., Sorry to say it in this way. This is not my type of
> communication. I guess a sense of humor is something we need for this
> season :). I feel bad knowing that you are not seeing the whole
> picture without replying to you.
>
> On Sat, Nov 28, 2009 at 6:51 AM, Richard McIntosh
> <richard.c.mcintosh@...> wrote:
> Well that’s good. I hope he brings something nice back with
> him.
>
> But seriously, has calibrate been removed from wacomcpl’s
> newest versions or is mine misconfigured/ missing dependancy
> ect. Any help would be appreciated.
>
> ----- Original message -----
>
> christmas with the folks, he'll be back in january
>
> (couldn't resist sorry)
>
> On Fri, 2009-11-27 at 16:07 +0100, Richard McIntosh wrote:
>
> > Hi
>
> > When running wacomcpl with my n-trig tablet pc. I get stylus
> and touch
>
> > come up in my select device list. When I select stylus I
> have the
>
> > options Feel, Tool Buttons, Tracking, Screen Mapping but no
> calibrate.
>
> > I am using 8.4.4 and was previously using 8.4.3 which also
> had no
>
> > calibrate button in wacomcpl. Does anyone know why it is
> missing?
>
> >
>
> > Richard
>
> >
>
> >
> ------------------------------------------------------------------------------
>
> > Let Crystal Reports handle the reporting - Free Crystal
> Reports 2008 30-Day
>
> > trial. Simplify your report design, integration and
> deployment - and focus on
>
> > what you do best, core application coding. Discover what's
> new with
>
> > Crystal Reports now. http://p.sf.net/sfu/bobj-july
>
> > _______________________________________________
>
> > Linuxwacom-discuss mailing list
>
> > Linuxwacom-discuss@...
>
> >
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal
> Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment
> - and focus on
> what you do best, core application coding. Discover what's new
> with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Linuxwacom-discuss mailing list
> Linuxwacom-discuss@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>
>

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 tablet buttons/wheel

2009-11-29T16:57:10Z

On Fri, Nov 27, 2009 at 04:50:38PM +0000, Taz Lodder wrote:

> Thanks for your fast response. That's actually what I thought, but I
> was copying the instructions from the ServerLayout page from here:
> http://linuxwacom.sourceforge.net/index.php/howto/srvlayout which do
> not mention this for the "pad" input device.
>
> Which don't give the pad any sort of event.
>
> Section "ServerLayout"
> Identifier "Default Layout"
> Screen 0 "Screen0" 0 0
> InputDevice "Mouse0" "CorePointer"
> InputDevice "Keyboard0" "CoreKeyboard"
> *InputDevice "stylus" "SendCoreEvents"
> InputDevice "eraser" "SendCoreEvents"
> InputDevice "cursor" "SendCoreEvents" # For non-LCD tablets only
> InputDevice "touch" "SendCoreEvents" # Only a few TabletPCs support this type
> InputDevice "pad" # For Intuos3/CintiqV5/Graphire4/Bamboo tablets*
> EndSection
>
> Anyway, I have added it, rebooted (just to make sure!) and that seems to have done the trick!
>
> Thank you so much for your help.

just FYI and for others that may be interested:
any device that should be able to interact with "core applications" (read:
apps that don't specifically accommodate for tablets) needs to be sending
core events. this is an X server distinction introduced by the X Input
Extension back in 94 to allow for more complex input features without
breaking the world.

in newer X servers SendCoreEvents is the default and doesn't require a
specific option anymore though from your logfile I couldn't tell what server
version you're running.

anyway - any device that isn't set to SendCoreEvents can only send events to
specialised apps (e.g. GIMP) and doesn't work in a "normal" manner. the easy
way to test - if the device moves the visible pointer it sends core events.

another thing - after changing the xorg.conf an X server restart is enough,
rebooting the box is not necessary.

Cheers,
Peter

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: no calibrate button on wacomcpl

2009-11-29T12:16:42Z

Hey Ping,

I think you misunderstood me. I am really grateful for all the work the
linux-wacom community does. Rereading my comment, I can see that it
could have been read as sarcastic in a negative way. I was just trying
to carry on the joke that Bezierk had made, while asking my question
again. Sorry to have caused offence. :)

I did try googling for the answer first and found lots of answers about
everything missing from wacomcpl and how to fix it. But nothing
describing my problem.

Richard

On Sun, 2009-11-29 at 10:32 -0800, Ping wrote:

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: no calibrate button on wacomcpl

2009-11-29T10:32:54Z

Hi Richard,

I think you've got "something nice" before Christmas - a working driver from Wacom and the linuxWacom community. It would be a time for you to bring something back to us in January :).

Ping

P.S., Sorry to say it in this way. This is not my type of communication. I guess a sense of humor is something we need for this season :). I feel bad knowing that you are not seeing the whole picture without replying to you.

On Sat, Nov 28, 2009 at 6:51 AM, Richard McIntosh <richard.c.mcintosh@...> wrote:

Well that’s good. I hope he brings something nice back with him.

But seriously, has calibrate been removed from wacomcpl’s newest versions or is mine misconfigured/ missing dependancy ect. Any help would be appreciated.

----- Original message -----

christmas with the folks, he'll be back in january

(couldn't resist sorry)

On Fri, 2009-11-27 at 16:07 +0100, Richard McIntosh wrote:

> Hi

> When running wacomcpl with my n-trig tablet pc. I get stylus and touch

> come up in my select device list. When I select stylus I have the

> options Feel, Tool Buttons, Tracking, Screen Mapping but no calibrate.

> I am using 8.4.4 and was previously using 8.4.3 which also had no

> calibrate button in wacomcpl. Does anyone know why it is missing?

>

> Richard

>

> ------------------------------------------------------------------------------

> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day

> trial. Simplify your report design, integration and deployment - and focus on

> what you do best, core application coding. Discover what's new with

> Crystal Reports now. http://p.sf.net/sfu/bobj-july

> _______________________________________________

> Linuxwacom-discuss mailing list

> Linuxwacom-discuss@...

> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: no calibrate button on wacomcpl

2009-11-28T06:51:07Z

Well that’s good. I hope he brings something nice back with him.

But seriously, has calibrate been removed from wacomcpl’s newest versions or is mine misconfigured/ missing dependancy ect. Any help would be appreciated.

----- Original message -----

christmas with the folks, he'll be back in january

(couldn't resist sorry)

On Fri, 2009-11-27 at 16:07 +0100, Richard McIntosh wrote:

> Hi

> When running wacomcpl with my n-trig tablet pc. I get stylus and touch

> come up in my select device list. When I select stylus I have the

> options Feel, Tool Buttons, Tracking, Screen Mapping but no calibrate.

> I am using 8.4.4 and was previously using 8.4.3 which also had no

> calibrate button in wacomcpl. Does anyone know why it is missing?

> Richard

> ------------------------------------------------------------------------------

> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day

> trial. Simplify your report design, integration and deployment - and focus on

> what you do best, core application coding. Discover what's new with

> Crystal Reports now. http://p.sf.net/sfu/bobj-july

> _______________________________________________

> Linuxwacom-discuss mailing list

> Linuxwacom-discuss@...

> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: no calibrate button on wacomcpl

2009-11-27T15:45:14Z

christmas with the folks, he'll be back in january

(couldn't resist sorry)

On Fri, 2009-11-27 at 16:07 +0100, Richard McIntosh wrote:

> Hi
> When running wacomcpl with my n-trig tablet pc. I get stylus and touch
> come up in my select device list. When I select stylus I have the
> options Feel, Tool Buttons, Tracking, Screen Mapping but no calibrate.
> I am using 8.4.4 and was previously using 8.4.3 which also had no
> calibrate button in wacomcpl. Does anyone know why it is missing?
>
> Richard
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Linuxwacom-discuss mailing list
> Linuxwacom-discuss@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: usbParse messages

2009-11-27T12:53:28Z

Hi Taz,

The problem has been fixed since 0.8.4-3. The exact fix was:

Fixed a serial number = 0 case in wcmUSB.c.

Please let me know if your testing result is different.

Ping

On Fri, Nov 27, 2009 at 4:36 AM, Taz Lodder <taz@...> wrote:

Hi Ping

Is there any news on this please. We are still stuck on driver 0.8.3-4 and as we buy more and more Intuos4 tablets, the requests for using the tablet buttons/wheel are increasing and so newer drivers would be useful here.

Thanks
Taz
taz lodder, tech department
-------------------------------------------------------
double negative, 77 shaftesbury avenue, london, w1d 5du
phone: +44 (0)20 7534 4400 fax: +44 (0)20 7534 4452
-------------------------------------------------------
Ping wrote:
I am trying to reproduce the issue here. Sreejith, please email your Xorg.0.log file to me directly (not to the list) after the problem happens.

Thank you,

Ping

On Sat, Sep 5, 2009 at 1:38 AM, Sreejith Sasidharan <replytosree@...> wrote:

Hi Ping,

I thing Chris having the same issue which I am having, When the pen goes out side of the stylus surface and back it takes time initialize, and some time the wacom behaves very strange,and it will not accept the commands of the user its losses its smooth flow, if we restart the machine it start working again smoothly.. is there is any new version will help us for the same
we having a memory of 16 GB and 8 Processors Xeon with Nvidea 1700 qudro

Thanks
Sreejith

On Sat, Sep 5, 2009 at 12:40 AM, Chris Banal <banal@...> wrote:

Hi Ping,

We are having a similar issue to the one Taz Lodder posted not long ago.
We're seeing the problem on our openSUSE 11.1 hosts running the 0.8.4
driver. The stylus will cut out and return after the mouse is moved.
We've also seen the pausing issue with the 0.8.3 driver. All previous
versions of the linuxwacom X driver. Segfault X when exiting KDE.

Thanks,
Chris

Re: Intuos4 tablet buttons/wheel

2009-11-27T08:51:58Z

Glad to help!

I couldn't remember how I had it set up before, and I have switched to HAL now, so I was guessing. :)

On Fri, Nov 27, 2009 at 10:50 AM, Taz Lodder <taz@...> wrote:

Hi Eric

Thanks for your fast response. That's actually what I thought, but I was copying the instructions from the ServerLayout page from 
here: http://linuxwacom.sourceforge.net/index.php/howto/srvlayout which do not mention this for the "pad" input device.

Which don't give the pad any sort of event.

Section "ServerLayout"
        Identifier     "Default Layout"
        Screen 0 "Screen0"   0 0
        InputDevice    "Mouse0"    "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "stylus"    "SendCoreEvents"
        InputDevice    "eraser"    "SendCoreEvents"
        InputDevice    "cursor"    "SendCoreEvents"    # For non-LCD tablets only
	InputDevice    "touch"     "SendCoreEvents"    # Only a few TabletPCs support this type
        InputDevice    "pad"   # For Intuos3/CintiqV5/Graphire4/Bamboo tablets
EndSection

Anyway, I have added it, rebooted (just to make sure!) and that seems to have done the trick!

Thank you so much for your help.

Taz
Eric Honaker wrote:
Shouldn't the pad have SendCoreEvents, too? Since the buttons act like mouse buttons?

On Fri, Nov 27, 2009 at 10:25 AM, Taz Lodder <taz@...> wrote:

For whatever reason, I just cannot get this to work.

I have configure/make/make install'd (using the --enable-wacom switch)
the latest wacom driver, 0.8.4-4. There were no errors. It didn't seem
to copy across wacom.ko so I copied that manually in the end and did
rmmod/modprobe/reboot.

xev shows that the tracking works ok and pen button-clicks are all
recognised, but clicking on the tablet buttons/wheel is not recognised.

The pad is recognised by wacomcpl and it displays pull-down menus for
all the tablet buttons, but obviously changing them has no effect.

Here is the output of some commands/files (all I can think of):

# dmesg | grep wacom
usbcore: registered new interface driver wacom
wacom: v1.49-pc-1:USB Wacom Graphire and Wacom Intuos tablet driver

# lsusb | grep -i wacom
Bus 002 Device 003: ID 056a:00b9 Wacom Co., Ltd

# cat /proc/bus/input/devices
I: Bus=0003 Vendor=056a Product=00b9 Version=0104
N: Name="Wacom Intuos4 6x9"
P: Phys=
S: Sysfs=/class/input/input5
U: Uniq=
H: Handlers=mouse2 event5
B: EV=1f
B: KEY=1cff 1f01ff 0 0 0 0
B: REL=100
B: ABS=1000f000167
B: MSC=1

The relevant parts of my xorg.conf file looks like this:
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "pad"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "pad"
Option "Device" "/dev/input/wacom"
Option "Type" "pad"
Option "USB" "on"
EndSection

The relevant bits of my Xorg.0.log looks like this:
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(**) Option "Device" "/dev/input/wacom"
stylus Wacom X driver grabbed event device
(==) Wacom USB Intuos4 tablet speed=9600 (38400) maxX=44704 maxY=27940
maxZ=2047 resX=5080 resY=5080 tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "pad" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080

I really cannot see what I am missing here. I can't fathom out why the
tablet buttons are not recognised, but everything else works as normal.
Please can you point me in the right direction?

Many thanks
Taz

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 tablet buttons/wheel

2009-11-27T08:50:38Z

Hi Eric

Thanks for your fast response. That's actually what I thought, but I was copying the instructions from the ServerLayout page from 
here: http://linuxwacom.sourceforge.net/index.php/howto/srvlayout which do not mention this for the "pad" input device.

Which don't give the pad any sort of event.

Section "ServerLayout"
        Identifier     "Default Layout"
        Screen 0 "Screen0"   0 0
        InputDevice    "Mouse0"    "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "stylus"    "SendCoreEvents"
        InputDevice    "eraser"    "SendCoreEvents"
        InputDevice    "cursor"    "SendCoreEvents"    # For non-LCD tablets only
	InputDevice    "touch"     "SendCoreEvents"    # Only a few TabletPCs support this type
        InputDevice    "pad"   # For Intuos3/CintiqV5/Graphire4/Bamboo tablets
EndSection

Anyway, I have added it, rebooted (just to make sure!) and that seems to have done the trick!

Thank you so much for your help.

Taz

Eric Honaker wrote:

Shouldn't the pad have SendCoreEvents, too? Since the buttons act like mouse buttons?

On Fri, Nov 27, 2009 at 10:25 AM, Taz Lodder <taz@...> wrote:

For whatever reason, I just cannot get this to work.

I have configure/make/make install'd (using the --enable-wacom switch)
the latest wacom driver, 0.8.4-4. There were no errors. It didn't seem
to copy across wacom.ko so I copied that manually in the end and did
rmmod/modprobe/reboot.

xev shows that the tracking works ok and pen button-clicks are all
recognised, but clicking on the tablet buttons/wheel is not recognised.

The pad is recognised by wacomcpl and it displays pull-down menus for
all the tablet buttons, but obviously changing them has no effect.

Here is the output of some commands/files (all I can think of):

# dmesg | grep wacom
usbcore: registered new interface driver wacom
wacom: v1.49-pc-1:USB Wacom Graphire and Wacom Intuos tablet driver

# lsusb | grep -i wacom
Bus 002 Device 003: ID 056a:00b9 Wacom Co., Ltd

# cat /proc/bus/input/devices
I: Bus=0003 Vendor=056a Product=00b9 Version=0104
N: Name="Wacom Intuos4 6x9"
P: Phys=
S: Sysfs=/class/input/input5
U: Uniq=
H: Handlers=mouse2 event5
B: EV=1f
B: KEY=1cff 1f01ff 0 0 0 0
B: REL=100
B: ABS=1000f000167
B: MSC=1

The relevant parts of my xorg.conf file looks like this:
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "pad"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "pad"
Option "Device" "/dev/input/wacom"
Option "Type" "pad"
Option "USB" "on"
EndSection

The relevant bits of my Xorg.0.log looks like this:
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(**) Option "Device" "/dev/input/wacom"
stylus Wacom X driver grabbed event device
(==) Wacom USB Intuos4 tablet speed=9600 (38400) maxX=44704 maxY=27940
maxZ=2047 resX=5080 resY=5080 tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "pad" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080

I really cannot see what I am missing here. I can't fathom out why the
tablet buttons are not recognised, but everything else works as normal.
Please can you point me in the right direction?

Many thanks
Taz

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 tablet buttons/wheel

2009-11-27T08:32:50Z

Shouldn't the pad have SendCoreEvents, too? Since the buttons act like mouse buttons?

On Fri, Nov 27, 2009 at 10:25 AM, Taz Lodder <taz@...> wrote:

For whatever reason, I just cannot get this to work.

I have configure/make/make install'd (using the --enable-wacom switch)
the latest wacom driver, 0.8.4-4. There were no errors. It didn't seem
to copy across wacom.ko so I copied that manually in the end and did
rmmod/modprobe/reboot.

xev shows that the tracking works ok and pen button-clicks are all
recognised, but clicking on the tablet buttons/wheel is not recognised.

The pad is recognised by wacomcpl and it displays pull-down menus for
all the tablet buttons, but obviously changing them has no effect.

Here is the output of some commands/files (all I can think of):

# dmesg | grep wacom
usbcore: registered new interface driver wacom
wacom: v1.49-pc-1:USB Wacom Graphire and Wacom Intuos tablet driver

# lsusb | grep -i wacom
Bus 002 Device 003: ID 056a:00b9 Wacom Co., Ltd

# cat /proc/bus/input/devices
I: Bus=0003 Vendor=056a Product=00b9 Version=0104
N: Name="Wacom Intuos4 6x9"
P: Phys=
S: Sysfs=/class/input/input5
U: Uniq=
H: Handlers=mouse2 event5
B: EV=1f
B: KEY=1cff 1f01ff 0 0 0 0
B: REL=100
B: ABS=1000f000167
B: MSC=1

The relevant parts of my xorg.conf file looks like this:
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "pad"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "pad"
Option "Device" "/dev/input/wacom"
Option "Type" "pad"
Option "USB" "on"
EndSection

The relevant bits of my Xorg.0.log looks like this:
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(**) Option "Device" "/dev/input/wacom"
stylus Wacom X driver grabbed event device
(==) Wacom USB Intuos4 tablet speed=9600 (38400) maxX=44704 maxY=27940
maxZ=2047 resX=5080 resY=5080 tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "pad" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080

I really cannot see what I am missing here. I can't fathom out why the
tablet buttons are not recognised, but everything else works as normal.
Please can you point me in the right direction?

Many thanks
Taz

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Intuos4 tablet buttons/wheel

2009-11-27T08:25:02Z

For whatever reason, I just cannot get this to work.

I have configure/make/make install'd (using the --enable-wacom switch)
the latest wacom driver, 0.8.4-4. There were no errors. It didn't seem
to copy across wacom.ko so I copied that manually in the end and did
rmmod/modprobe/reboot.

xev shows that the tracking works ok and pen button-clicks are all
recognised, but clicking on the tablet buttons/wheel is not recognised.

The pad is recognised by wacomcpl and it displays pull-down menus for
all the tablet buttons, but obviously changing them has no effect.

Here is the output of some commands/files (all I can think of):

# dmesg | grep wacom
usbcore: registered new interface driver wacom
wacom: v1.49-pc-1:USB Wacom Graphire and Wacom Intuos tablet driver

# lsusb | grep -i wacom
Bus 002 Device 003: ID 056a:00b9 Wacom Co., Ltd

# cat /proc/bus/input/devices
I: Bus=0003 Vendor=056a Product=00b9 Version=0104
N: Name="Wacom Intuos4 6x9"
P: Phys=
S: Sysfs=/class/input/input5
U: Uniq=
H: Handlers=mouse2 event5
B: EV=1f
B: KEY=1cff 1f01ff 0 0 0 0
B: REL=100
B: ABS=1000f000167
B: MSC=1

The relevant parts of my xorg.conf file looks like this:
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "pad"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "pad"
Option "Device" "/dev/input/wacom"
Option "Type" "pad"
Option "USB" "on"
EndSection

The relevant bits of my Xorg.0.log looks like this:
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(**) Option "Device" "/dev/input/wacom"
stylus Wacom X driver grabbed event device
(==) Wacom USB Intuos4 tablet speed=9600 (38400) maxX=44704 maxY=27940
maxZ=2047 resX=5080 resY=5080 tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "pad" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080

I really cannot see what I am missing here. I can't fathom out why the
tablet buttons are not recognised, but everything else works as normal.
Please can you point me in the right direction?

Many thanks
Taz

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: no calibrate button on wacomcpl

2009-11-27T07:07:49Z

Hi
When running wacomcpl with my n-trig tablet pc. I get stylus and touch
come up in my select device list. When I select stylus I have the
options Feel, Tool Buttons, Tracking, Screen Mapping but no calibrate.
I am using 8.4.4 and was previously using 8.4.3 which also had no
calibrate button in wacomcpl. Does anyone know why it is missing?

Richard

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: usbParse messages

2009-11-27T04:36:47Z

Hi Ping

Is there any news on this please. We are still stuck on driver 0.8.3-4 and as we buy more and more Intuos4 tablets, the requests for using the tablet buttons/wheel are increasing and so newer drivers would be useful here.

Thanks
Taz

taz lodder, tech department
-------------------------------------------------------
double negative, 77 shaftesbury avenue, london, w1d 5du
phone: +44 (0)20 7534 4400 fax: +44 (0)20 7534 4452
-------------------------------------------------------

Ping wrote:

I am trying to reproduce the issue here. Sreejith, please email your Xorg.0.log file to me directly (not to the list) after the problem happens.

Thank you,

Ping

On Sat, Sep 5, 2009 at 1:38 AM, Sreejith Sasidharan <replytosree@...> wrote:

Hi Ping,

I thing Chris having the same issue which I am having, When the pen goes out side of the stylus surface and back it takes time initialize, and some time the wacom behaves very strange,and it will not accept the commands of the user its losses its smooth flow, if we restart the machine it start working again smoothly.. is there is any new version will help us for the same
we having a memory of 16 GB and 8 Processors Xeon with Nvidea 1700 qudro

Thanks
Sreejith

On Sat, Sep 5, 2009 at 12:40 AM, Chris Banal <banal@...> wrote:

Hi Ping,

We are having a similar issue to the one Taz Lodder posted not long ago.
We're seeing the problem on our openSUSE 11.1 hosts running the 0.8.4
driver. The stylus will cut out and return after the mouse is moved.
We've also seen the pausing issue with the 0.8.3 driver. All previous
versions of the linuxwacom X driver. Segfault X when exiting KDE.

Thanks,
Chris
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
  

Re: Wacom Intuos4, xorg 1.7.1

2009-11-24T16:53:03Z

On Tue, Nov 24, 2009 at 01:47:34PM +0100, linuxwacomdiscuss wrote:

> I am unfortunately not in goal yet,
> The make install generates the wacom_drv.so file in the /usr/.../input dir.
>
> When I look into the log files, I see
> Nov 24 12:40:01 localhost kernel: wacom: v1.51:USB Wacom Graphire
> and Wacom Intuos tablet driver
> This is the only hint of a driver version I can find in the log files.
>
> I have attached the messages and Xorg.0.log logfiles and my xorg.conf file
>
> Status of the usage is still, the cursor follows the pen, but pen buttons
> doesn't work. The hard buttons on the tablet does in some cases act as a
> mouse click (in the shell, but not in dialogs or apps).
>
> Thank you for your support,

looking at the log, the device isn't initialized at all. this is due to the
xorg.conf, although you have the matching sections in the config file, they
aren't referenced. The ServerLayout only references the Mouse0 device, not
the others, hence the server doesn't try to initialize them.

It's not overly well known, but a single xorg.conf can contain multiple
independent configurations. So the following xorg.conf is valid

----%<--------------------------------------------
Section "ServerLayout"
Identifier "mouse only"
InputDevice "mouse" "CorePointer"
InputDevice "keyboard" "CoreKeyboard"
...
EndSection

Section "ServerLayout"
Identifier "wacom"
InputDevice "mouse" "CorePointer"
InputDevice "keyboard" "CoreKeyboard"
InputDevice "wacom stylus"
InputDevice "wacom erasor"
...
EndSection

[... skipped for brevity]
---%<---------------------------------------------

then you can pick which one to use at startup time, e.g.
$> Xorg -layout "wacom"

for this reason, the server will only initialize the input devices
referenced in the chosen server layout (default: the first one). If other
devices are present but not referenced, they're ignored.
There's some special handling for when no server layout is present or no
input devices are referenced at all but I'll skip those cases.

on top of this - you didn't disable hotplugging. so the mouse and kbd
devices are disabled by the server and instead all devices presented by HAL
are added. the wacom device is added with the evdev driver (default driver
for input devices). this again hints that the HAL setup is missing, most
likely the wacom.fdi isn't in the right place. Try to put it into hal's
/fdi/policy directory and restart hal. then check with lshal that the
input.x11_driver option is set to "wacom" for these devices.

Alternatively, if you refernence the devices from the ServerLayout, that'll
work as well.

complicated, I know. that's why we're trying to push more towards having
everything hotplugged, all you need then is the right configuration files in
place (in this case wacom.fdi) and the rest automagically happens. most of
the time, anyway.

Cheers,
Peter

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Wacom Intuos4, xorg 1.7.1

2009-11-23T13:48:50Z

On Mon, Nov 23, 2009 at 01:02:33PM -0800, Ping wrote:
> Issue:
>
> -----------------------------------------
> su
> cp src/.libs/wacom_drv.so /usr/lib/xorg/modules/input
> ------------------------------------------
>
> If you are running x86_64, use /usr/lib64/xorg/modules/input instead. That
> what I do, Peter may have other suggestions.

by default, configure assumes a prefix of /usr/local. most distributions use
a prefix of /usr however, so the configure command should be

./configure --prefix=/usr

as Ping said, if you're on 64 bit the libraries may be in /usr/lib64 so you
probably need to append the specific libdir
./configure --prefix=/usr --libdir=/usr/lib64

i think those two should be enough to allow for a make install that replaces
the driver and a quick check is to search for wacom_drv.so - it has to be in
the same directory as evdev_drv.so

once the install succeeds, please check that the driver is attempted to be
loaded (i.e. either xorg.conf or HAL are set up correctly) and that the
version number of the driver is correct (0.10.0). That'll tell you then if
the installation failed or there is in fact a driver issue. Checking the log
will answer both of these questions.

Cheers,
Peter

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Wacom Intuos4, xorg 1.7.1

2009-11-23T13:02:33Z

Issue:

-----------------------------------------
su
cp src/.libs/wacom_drv.so /usr/lib/xorg/modules/input
------------------------------------------

If you are running x86_64, use /usr/lib64/xorg/modules/input instead. That what I do, Peter may have other suggestions.

Ping

On Mon, Nov 23, 2009 at 5:22 AM, linuxwacomdiscuss <linuxwacomdiscuss@...> wrote:

Hi Ping

Thanks for the reply.

I have found the driver, and successfully configured and compiled it (make + make install), but (excuse my lack of linux insight) it doesn’t seem like the driver has been replaced.

What is the steps to install it.

I have:

                ./autogen.sh

                ./configure

                make

                make install

All passes without error messages.

Regards

Casper Dietrich

From: Ping [mailto:pinglinux@...]
Sent: 22. november 2009 22:33
To: linuxwacomdiscuss@...
Cc: linuxwacom-discuss@...
Subject: Re: [Linuxwacom-discuss] Wacom Intuos4, xorg 1.7.1

You need to build the driver off xf86-input-wacom since linuxwacom-0.8.4-4 doesn't support x server 1.7+.

Ping

Re: Wacom Intuos4, xorg 1.7.1

2009-11-23T05:22:54Z

Hi Ping

Thanks for the reply.

I have found the driver, and successfully configured and compiled it (make + make install), but (excuse my lack of linux insight) it doesn’t seem like the driver has been replaced.

What is the steps to install it.

I have:

./autogen.sh

./configure

make

make install

All passes without error messages.

Regards

Casper Dietrich

From: Ping [mailto:pinglinux@...]
Sent: 22. november 2009 22:33
To: linuxwacomdiscuss@...
Cc: linuxwacom-discuss@...
Subject: Re: [Linuxwacom-discuss] Wacom Intuos4, xorg 1.7.1

You need to build the driver off xf86-input-wacom since linuxwacom-0.8.4-4 doesn't support x server 1.7+.

Ping

---------- Forwarded message ----------
From: Peter Hutterer <peter.hutterer@...>
Date: Thu, Nov 19, 2009 at 7:49 PM
Subject: [ANNOUNCE] xf86-input-wacom 0.10.1

Release 0.10.1 of the xf86-input-wacom driver is now available.
Note that this driver currently resides in my $HOME on freedesktop.org.

http://cgit.freedesktop.org/~whot/xf86-input-wacom/

Loads of patches, mostly cleanup and aimed towards better hotplugging
support. Instead of relying on HAL directives, the driver now does its own
hotplugging based on the model found. To do so, the driver queries the
kernel for the tablet's capabilities and then sets up stylus, erasor, etc.
pending the matching keys set on the device.

Peter Hutterer (45):
Use the SYSCALL macro for opening the fd
Silence compiler warnings if DEBUG is off.
Abstract the vendor ID into a #define
Don't cast xalloc returns.
Streamline xf86WcmAllocate a bit
Localize lookup for other devices of the same device.
Unify log messages to a common format.
Move allocation of type out of xf86WcmInit
Fix a comment
Remove fakeLocal init device.
Don't overwrite the name with the XI type.
Remove needless NULL checks before xfree.
Use ARRAY_SIZE macro instead of manual sizeof().
Pass type into wcmIsAValidType.
Break out of the loop once we found a valid type.
Abstract product lookup into a static function.
On unplug, remove the device from the commonWcmDevices list.
Support auto-hotplugging in the driver.
Remove unecessary debug statements.
Don't accept invalid Rotate and ForceDevice options.
vim tags for the coding style.
BaudRate only needs checking for ISDV4 devices.
Remove Xfree86 4 serial wrapper defines
Remove some more useless defines.
Rip most option parsing out of xf86WcmInit.
Remove log spamming debug message.
Remove a needless call to xf86CheckStrOption
Move the uniq assignment into wcmNeedAutoHotplug.
Move auto-dev probing checks into small static function
Remove "grabbed event device" log message.
Export tool type as Wacom Tool Type property.
Don't fail just because it's not a wacom tablet.
Add 0xFF product as catchall for unknown devices.
Add wacom-properties header file.
Fix an error message to list the device name.
If a device is specified, don't check for a wacom vendor id.
Remove some if 0'd code.
Remove spurious executable bits from source files.
Add GPL document to dist tarball.
Fix long-standing typos in applying speed factors.
Remove REVISION HISTORY comments.
Remove defines from the ghost of christmas past.
Purge driver-specific speed/accel.
Fix comment in configure.
wacom 0.10.1

Ping Cheng (9):
Avoid adding duplicated devices/tools from hotplugging
Validate tool type before adding it
share device size and resolution between penabled and touch of the same product ID
process second finger touch data
report device id for protocol 5 devices
Spin-off validatation from configuration.
retrieve all tool types from the kernel
This patch allows multiple tools of the same type to be defined for one device.
Remove a duplicated #ifdef in wcmValidateDevice.c

Przemo Firszt (1):
Remove duplicate of #include "xf86Wacom.h" and #include "wcmFilter.h"

Thomas Jaeger (1):
Fix TPCButton option

git tag: xf86-input-wacom-0.10.1

http://people.freedesktop.org/~whot/xf86-input-wacom/xf86-input-wacom-0.10.1.tar.bz2
MD5: 544f40bb5bcdd8538c248c4067f3848f xf86-input-wacom-0.10.1.tar.bz2
SHA1: 106f7fcf9e4255b5b3efa29bccc8ed94d42cfb2d xf86-input-wacom-0.10.1.tar.bz2

http://people.freedesktop.org/~whot/xf86-input-wacom/xf86-input-wacom-0.10.1.tar.gz
MD5: aa7ab1aa876276ca2d8aac115671c841 xf86-input-wacom-0.10.1.tar.gz
SHA1: 0c3358ad37fb83024cdca2f2ed4ad219d74d1e97 xf86-input-wacom-0.10.1.tar.gz

On Sun, Nov 22, 2009 at 8:49 AM, <linuxwacomdiscuss@...> wrote:

Re: Wacom Intuos4, xorg 1.7.1

2009-11-22T13:33:18Z

You need to build the driver off xf86-input-wacom since linuxwacom-0.8.4-4 doesn't support x server 1.7+.

Ping

On Sun, Nov 22, 2009 at 8:49 AM, <linuxwacomdiscuss@...> wrote:

Hi

I’m trying to install a linux PC, with the main purpose to run X towards servers. i.e. no local apps (except ssh and kernel ….)
I need my wacom Intuos4 to work on the system.

I have had several attempts, without luck.
My current setup is a IBM R51 laptop with Fedora 12 (new installation)

It seems that the point where I get stuck is that the current drivers for wacom only supports up to xorg 1.6, my kernel runs 1.7.1.

Installation overview
Uname –r = 2.6.31.5-127.fc12.i686
Linuxwacom-0.8.4-4
./prebuild/install fails
Make fails with compile error on argument count for functions: ‘InitValuatorAxisStruct’, ‘InitButtonClassDevicsStruct’… -> this is due to xorg 1.6 / 1.7.1 definitions
The tablet can move the mouse pointer, but clicks and buttins are not functional.
The wacom Is present in /proc/bus/usb/devices and /proc/bus/input/devices

Can anyone point to a solution that works, I don’t care if it is fedora, ubunto or any other distribution, and what release to use.

Thanks

Casper Dietrich

Wacom Intuos4, xorg 1.7.1

2009-11-22T08:49:25Z

Hi

I’m trying to install a linux PC, with the main purpose to run X towards servers. i.e. no local apps (except ssh and kernel ….)
I need my wacom Intuos4 to work on the system.

I have had several attempts, without luck.
My current setup is a IBM R51 laptop with Fedora 12 (new installation)

It seems that the point where I get stuck is that the current drivers for wacom only supports up to xorg 1.6, my kernel runs 1.7.1.

Installation overview
Uname –r = 2.6.31.5-127.fc12.i686
Linuxwacom-0.8.4-4
./prebuild/install fails
Make fails with compile error on argument count for functions: ‘InitValuatorAxisStruct’, ‘InitButtonClassDevicsStruct’… -> this is due to xorg 1.6 / 1.7.1 definitions
The tablet can move the mouse pointer, but clicks and buttins are not functional.
The wacom Is present in /proc/bus/usb/devices and /proc/bus/input/devices

Can anyone point to a solution that works, I don’t care if it is fedora, ubunto or any other distribution, and what release to use.

Thanks

Casper Dietrich

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: A Multi-Monitor Question

2009-11-21T11:45:06Z

On 11/19/2009 10:16 PM, Alexander Roalter wrote:

> On 11/19/2009 10:03 PM, Alexander Roalter wrote:
>> On 11/19/2009 04:38 AM, Ping wrote:
>>> Please see my comments in line.
>>>
>>> Ping
>>>
>>> On Wed, Nov 18, 2009 at 2:46 PM, Alexander Roalter <alexander@...
>>> <mailto:alexander@...>> wrote:
>>>
>>> After a long delay, I was finally able to update my X and other things,
>>> and after removing a superfluous twinview option I forgot in the
>>> keyboard section of the xorg.conf, I now can use the tablet (Graphire4),
>>> and with xsetwacom set Stylus0 Screen_No n set it to different monitors.
>>>
>>> I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
>>> desktop.
>>>
>>> If I though start the gimp or inkscape and use the XInput capabilities,
>>> I get the ordinary mouse arrow right where it belongs, but the drawing
>>> is done as if the entire desktop was used (therefore drawing a perfect
>>> circle on the tablet, I get an ellipse which is three times as wide as
>>> it is high.
>>>
>>>
>>> Did you try the "KeepShape" option. The problem is that your tablet has
>>> a different width and height ration with your screen. If you use
>>> KeepShape, don't forget your other mappings, such as topX/Y and
>>> bottomX/Y will not work any more.
>>
>> Ok, tested that and it was worse than before, since only a tiny fraction
>> of the tablet is used anymore, and the behavior in x-direction remains
>> the same, in y direction now I can only paint on roughly 1/3rd of the
>> height -> even more distortion.
>>
>>>
>>>
>>> Which linuxwacom are you running? 0.8.5-4 removes the duplicated
>>> devices for you automatically. Any version older than that will give
>>> you two sets of devices if you have one defined in your xorg.conf. You
>>> could disable the hotplugging one by modifying the wacom fdi file under
>>> /local/share/hal/fdi/policy/20thirdparty (10-linuxwacom.fdi on Fedora.
>>> I am not exactly sure where the file is located on your platform. The
>>> name could be different too.).
>>
>> Tried now 0.8.5-4, with kernel module also, still the same results.
>>
>> I removed the fdi file and am now working with my self-set up files in
>> /etc/X11/xorg.conf (Stylus0, Eraser0, Pad0); Still, a device "Wacom
>> Graphire4 6x8" (without " pad", " eraser" or " cursor" extension added
>> => before I had 4 of these devices, and I don't know where this device
>> is specified) is in the list, but there's no problem (apparently) with
>> it, so simply don't use it.
>>
>> Since the cursor is displayed always on the correct position (but the
>> arrows on inkscape's rulers don't), I assume this is probably an X
>> error/problem. xidump displays values from 0 to 16000 (roughly), and I'm
>> not sure who does the computing for the output into the different input
>> streams =>
>>
>> Does X11 receive only one data stream from the driver containing the
>> absolute coordinates (0-16000 in both directions, together with
>> pressure, tilt etc), or does X11 receive both the exact data (XInput?)
>> as well as preprocessed data it uses when not in XInput mode, which then
>> is used to place the normal cursor? At least that's what I think is
>> happening here:
>>
>>
>> driver =====Normal Input Channel =====> X11 (delivers coordinates from
>> 0 to 1680, 0 to 1050 as well as
>> pressed buttons when in absolute
>> mode, -1..+1 in both directions
>> when in relative mode.
>>
>> driver =====XInput Channel ==========> X11 (delivers coordinates from
>> 0 to 16384, 0 to 16384 and
>> pressure and tilt and whatever
>> else to X11.
>>
>> or is it different, and the XInput Channel already gets again data from
>> 0 to 1680 (or erroneously from 0 to 5280) to X11? If this is the case,
>> then it probably is a driver problem, but if X gets the original data
>> and does the computing by itself, then it's clearly an X problem (or the
>> Wacom driver for X, if any)
>>
>
> Hm, it can also be a GTK problem (i don't have any non-gtk XInput aware
> apps), so this thread might help (and keep the blame off the wacom driver):
>
> http://www.gimpusers.com/forums/gimp-developer/10806-xinerama-and-wacom.html
>
>

To finalize this, I've now been able to recompile GTK+ with a (modified)
patch, and now it's all working as expected *hooray*

it is all in gdk/x11/gdkinput-x11.c, line 455 (Version 2.18.3) and forth:

if (gdkdev->info.mode == GDK_MODE_SCREEN)
{
int core_pointer_x, core_pointer_y, cur_monitor;
GdkRectangle mon_geometry;
GdkScreen *cur_screen;

gdk_display_get_pointer(gdk_drawable_get_display(window),
&cur_screen,
&core_pointer_x,
&core_pointer_y,
0);
cur_monitor = gdk_screen_get_monitor_at_point(cur_screen,
core_pointer_x,
core_pointer_y);

gdk_screen_get_monitor_geometry(cur_screen,
cur_monitor,
&mon_geometry);
/*
x_scale = gdk_screen_get_width (gdk_drawable_get_screen (window))
/ device_width;
y_scale = gdk_screen_get_height (gdk_drawable_get_screen (window))
/ device_height;
*/
x_scale = mon_geometry.width / device_width;
y_scale = mon_geometry.height / device_height;

x_offset = - impl_window->input_window->root_x - priv->abs_x;
y_offset = - impl_window->input_window->root_y - priv->abs_y;
}

Don't forget to compile gtk+ with --with-xinput=yes, otherwise there
will be no support for XInput altogether in GTK applications (GIMP,
Inkscape, ...)

--
Cheers,
Alex

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Pen release event not registered

2009-11-21T11:44:24Z

On 11/21/2009 08:32 PM, Ping wrote:
> So, it is not a driver issue, right? I was planning to test 0.8.5
> during the weekend...
>
> Ping
>
Hm, it seems I posted the patch to the wrong thread (b/c the patch was
for the multi-monitor thing which was wrongly evaluated by the GTK XInput.

The issue with the "mouse"-up event not being recognized at times with
the 0.8.5 still remains... So I went back to 0.8.4.

Sorry for the confusion.

--
Cheers,
Alex

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Pen release event not registered

2009-11-21T11:32:24Z

So, it is not a driver issue, right? I was planning to test 0.8.5 during the weekend...

Ping

On Sat, Nov 21, 2009 at 11:18 AM, Alexander Roalter <alexander@...> wrote:

On 11/20/2009 10:18 PM, Alexander Roalter wrote:
> On 11/20/2009 10:07 PM, Alexander Roalter wrote:
>> I'm using the wacom 0.8.5-4 driver, and X 1.6, with Inkscape and Gimp.
>>
>> Apart from the problems with multi monitor setup I have, setting the
>> stylus to Disabled (and thus not delivering Pressure information, but
>> still the normal coordinates and press/no press events), I sometimes
>> (also with setting Screen) get the problem that I press on the tablet on
>> say an object in Inkscape, drag it along, and after releasing the pen
>> from the tablet (but not out of range for the cursor to be detected), X
>> (or whoever else) doesn't get a proper 'MouseUp' event and continues
>> moving the object around.
>>
>> Since I've updated my entire system to opensuse 11.2 (from 11.0 with X
>> 1.4 and 0.8.3 driver) I'm not sure where this behavior came from and if
>> it is a driver issue or on a higher level in X.
>>
>> Did somebody experience something similar? It is really annoying and
>> sometimes very hard drawing something and after having finished a
>> move/stroke/whatever, the action goes on until you lift the pen this far
>> up that it goes out of range, otherwise it'll continue drawing/moving/etc.
>>
> One addition: using the 0.8.4-4 driver (the non beta one), I don't get
> this behavior (on a cursory check for about 10 minutes of heavy
> drawing/dragging etc.)
>

To finalize this, I've now been able to recompile GTK+ with a (modified)
patch, and now it's all working as expected *hooray*

it is all in gdk/x11/gdkinput-x11.c, line 455 (Version 2.18.3) and forth:

if (gdkdev->info.mode == GDK_MODE_SCREEN)
{
int core_pointer_x, core_pointer_y, cur_monitor;
GdkRectangle mon_geometry;
GdkScreen *cur_screen;

gdk_display_get_pointer(gdk_drawable_get_display(window),
&cur_screen,
&core_pointer_x,
&core_pointer_y,
0);
cur_monitor = gdk_screen_get_monitor_at_point(cur_screen,
core_pointer_x,
core_pointer_y);

gdk_screen_get_monitor_geometry(cur_screen,
cur_monitor,
&mon_geometry);
/*
x_scale = gdk_screen_get_width (gdk_drawable_get_screen (window))
/ device_width;
y_scale = gdk_screen_get_height (gdk_drawable_get_screen (window))
/ device_height;
*/
x_scale = mon_geometry.width / device_width;
y_scale = mon_geometry.height / device_height;

x_offset = - impl_window->input_window->root_x - priv->abs_x;
y_offset = - impl_window->input_window->root_y - priv->abs_y;
}

Don't forget to compile gtk+ with --with-xinput=yes, otherwise there
will be no support for XInput altogether in GTK applications (GIMP,
Inkscape, ...)

--
Cheers,
Alex

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Pen release event not registered

2009-11-21T11:18:16Z

On 11/20/2009 10:18 PM, Alexander Roalter wrote:

> On 11/20/2009 10:07 PM, Alexander Roalter wrote:
>> I'm using the wacom 0.8.5-4 driver, and X 1.6, with Inkscape and Gimp.
>>
>> Apart from the problems with multi monitor setup I have, setting the
>> stylus to Disabled (and thus not delivering Pressure information, but
>> still the normal coordinates and press/no press events), I sometimes
>> (also with setting Screen) get the problem that I press on the tablet on
>> say an object in Inkscape, drag it along, and after releasing the pen
>> from the tablet (but not out of range for the cursor to be detected), X
>> (or whoever else) doesn't get a proper 'MouseUp' event and continues
>> moving the object around.
>>
>> Since I've updated my entire system to opensuse 11.2 (from 11.0 with X
>> 1.4 and 0.8.3 driver) I'm not sure where this behavior came from and if
>> it is a driver issue or on a higher level in X.
>>
>> Did somebody experience something similar? It is really annoying and
>> sometimes very hard drawing something and after having finished a
>> move/stroke/whatever, the action goes on until you lift the pen this far
>> up that it goes out of range, otherwise it'll continue drawing/moving/etc.
>>
> One addition: using the 0.8.4-4 driver (the non beta one), I don't get
> this behavior (on a cursory check for about 10 minutes of heavy
> drawing/dragging etc.)
>

Re: Pen release event not registered

2009-11-20T13:18:39Z

On 11/20/2009 10:07 PM, Alexander Roalter wrote:

> I'm using the wacom 0.8.5-4 driver, and X 1.6, with Inkscape and Gimp.
>
> Apart from the problems with multi monitor setup I have, setting the
> stylus to Disabled (and thus not delivering Pressure information, but
> still the normal coordinates and press/no press events), I sometimes
> (also with setting Screen) get the problem that I press on the tablet on
> say an object in Inkscape, drag it along, and after releasing the pen
> from the tablet (but not out of range for the cursor to be detected), X
> (or whoever else) doesn't get a proper 'MouseUp' event and continues
> moving the object around.
>
> Since I've updated my entire system to opensuse 11.2 (from 11.0 with X
> 1.4 and 0.8.3 driver) I'm not sure where this behavior came from and if
> it is a driver issue or on a higher level in X.
>
> Did somebody experience something similar? It is really annoying and
> sometimes very hard drawing something and after having finished a
> move/stroke/whatever, the action goes on until you lift the pen this far
> up that it goes out of range, otherwise it'll continue drawing/moving/etc.
>

One addition: using the 0.8.4-4 driver (the non beta one), I don't get
this behavior (on a cursory check for about 10 minutes of heavy
drawing/dragging etc.)

--
Cheers,
Alex

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Pen release event not registered

2009-11-20T13:07:57Z

I'm using the wacom 0.8.5-4 driver, and X 1.6, with Inkscape and Gimp.

Apart from the problems with multi monitor setup I have, setting the
stylus to Disabled (and thus not delivering Pressure information, but
still the normal coordinates and press/no press events), I sometimes
(also with setting Screen) get the problem that I press on the tablet on
say an object in Inkscape, drag it along, and after releasing the pen
from the tablet (but not out of range for the cursor to be detected), X
(or whoever else) doesn't get a proper 'MouseUp' event and continues
moving the object around.

Since I've updated my entire system to opensuse 11.2 (from 11.0 with X
1.4 and 0.8.3 driver) I'm not sure where this behavior came from and if
it is a driver issue or on a higher level in X.

Did somebody experience something similar? It is really annoying and
sometimes very hard drawing something and after having finished a
move/stroke/whatever, the action goes on until you lift the pen this far
up that it goes out of range, otherwise it'll continue drawing/moving/etc.

--
Cheers,
Alex

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

touch and pen tablet error

2009-11-20T09:34:50Z

hi all,
i've a problem, I want change my old tablet and I buy a touch and pen.
I have the old driver for wacom 0.8.2.2, with this driver my new
tablet don't run and if I try to check it, the system say me:

no one software or directory.

I have this package installed:

wacom-tools
xserver-xorg-input-wacom

kernel 2.6.28-16

I try also to install new driver instead old, but the tablet don't run again.

I need 2.6.31 as kernel or I lost some package, some one can help me please?

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: A Multi-Monitor Question

2009-11-20T01:25:32Z

David De La Harpe Golden wrote:

> 2009/11/18 Alexander Roalter <alexander@...>:
>> After a long delay, I was finally able to update my X and other things,
>> and after removing a superfluous twinview option I forgot in the
>> keyboard section of the xorg.conf, I now can use the tablet (Graphire4),
>> and with xsetwacom set Stylus0 Screen_No n set it to different monitors.
>>
>> I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
>> desktop.
>
> classic "xinerama" or "xrandr" ? I'm guessing the former given your
> config snippet,
> but if you are using or can switch to the latter (and though if you've
> got three screens,
> unless you have a triple-output card, that may be unlikely), you can (ab)use
> calibration values to map wacom devices to rectangular subareas of the
> merged display.
>
> e.g. say that was a single xrandr desktop, so 5280x1080
>
> From your log:
> Tablet width in device coordinates: 16704
> Tablet height in device coordinates: 12064
>
> Say you want to map the tablet to the middle screen. The trick is to set
> TopX/TopY/BottomX/BottomY to the top-left and bottom-right of the entire
> _x11_ screen (5280x1080) in _device_ coordinates, assuming the tablet
> is "on" only the subarea of the screen of interest.
>
> Let's take the middle screen.
>
> It's a horizontal setup, so these two are easy:
> TopY: 0
> BottomY: 12064
>
> How about TopX?
>
> TopX: -16704 (by symmetry)
>
> How about BottomX?
>
> 16704 + (16704 / 1680 * 1920) = 33984
>
> So, to map stylus to middle screen:
>
> xsetwacom set stylus TopX -16704
> xsetwacom set stylus TopY 0
> xsetwacom set stylus BottomX 33984
> xsetwacom set stylus BottomY 12064
>
>
> Those values probably won't work properly for classic "xinerama" setups.
>
> I may have made dumb mistakes in the above (it's 2:30am here).
>
> Yes, I might manage to release a tool to automate the calculation some day...

I'll have to see, if I can put randr in there, as xinerama currently
works fine for all other applications. As I mentioned in the other
posting (from 9:16pm GMT), the specified behavior is probably a GTK
error, but I couldn't check it for correct behavior, b/c when I
installed a patched gtk version, I did not get any Extended Input
Devices at all (probably some headers missing and configure then
disabled support, but I don't know which headers *are* missing. I'll
have to toy around with it)

--
cheers,
Alex

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: A Multi-Monitor Question

2009-11-20T01:13:05Z

David De La Harpe Golden wrote:

--
cheers,
Alex

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Linuxwacom-discuss Digest, Vol 42, Issue 8

2009-11-19T13:33:32Z

How do I unsubscribe?

linuxwacom-discuss-request@... wrote:

Send Linuxwacom-discuss mailing list submissions to
	linuxwacom-discuss@...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
or, via email, send a message with subject or body 'help' to
	linuxwacom-discuss-request@...

You can reach the person managing the list at
	linuxwacom-discuss-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Linuxwacom-discuss digest..."


Today's Topics:

   1. Re: A Multi-Monitor Question (Kelly Price)
   2. Re: A Multi-Monitor Question (Ping)
   3. Re: A Multi-Monitor Question (Alexander Roalter)


----------------------------------------------------------------------

Message: 1
Date: Wed, 18 Nov 2009 22:17:00 -0500
From: Kelly Price strredwolf@...
Subject: Re: [Linuxwacom-discuss] A Multi-Monitor Question
To: Eric Honaker songwindapogee@...
Cc: linuxwacom-discuss@...
Message-ID:
	7ff566830911181917q5a9ec9beh7ba7f7ac144c8b8d@...
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Nov 18, 2009 at 8:29 PM, Eric Honaker
songwindapogee@... wrote:

I have wondered about that, actually.? Doesn't the Cintiq act like an extra monitor?? Wouldn't the issue be the same?

Or are you thinking you would just run your Cintiq in "clone" mode?


No, actually I'd run the Cintiq side-by-side as it does pipe VGA into
the screen under the tablet.  I just got to find that normal (not
wide-screen) one that does 1600x1200, which will match the height of
the 1920x1200 screen.  That way, I can run twinview on the NVidia
card.

Kelly Price wrote:

On Wed, Nov 18, 2009 at 5:46 PM, Alexander Roalter alexander@... wrote:


I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
desktop.



(snip)


The Thing is: removing my definitions from the xorg.conf, I still get a
workable cursor, but it spans over the entire desktop, that is, in the
first third of the tablet I get the first third of the first monitor, in
the 2nd third of the tablet I get the second third of the second
monitor, etc.

Monitors:
+------------++------------++---------------+
|111 ? ? ? ? || ? ?222 ? ? || ? ? ? ? ? 3333|
|111 ? ? ? ? || ? ?222 ? ? || ? ? ? ? ? 3333|
|111 ? ? ? ? || ? ?222 ? ? || ? ? ? ? ? 3333|
+------------++------------++_______________+

Tablet ? ?+-----+
? ? ? ? ?|1|2|3|
? ? ? ? ?+-----+

each part of the tablet maps to the corresponding field on the
corresponding monitor... ?(which is bad)



(snip)


And I don't see where I can change the behavior for the XInput, so that
even in screen mode it works correctly and takes the width of the
current screen, and not the combined width.



I had the same problem, with a similar setup (two monitor, similar to
your #2/#3 setup).  I disabled screen mode in Gimp and made sure the
Xwindows config was sane in order to get the Graphire4 I have working
properly.  Now if I can get it to a setup I can use and works with KDE
4.x, all will be well.  Unfortunately, KDE 4 doesn't play nice with
multiscreen (as seperate X screens) setups.

I might as well save up for a Cintque.



--
Eric Honaker
Dragonsept Arts and Publishing
PGP Public Key: F1BC60E6
"Words are, of course, the most powerful drug used by mankind." -- Rudyard Kipling



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



------------------------------

Message: 2
Date: Wed, 18 Nov 2009 19:38:50 -0800
From: Ping pinglinux@...
Subject: Re: [Linuxwacom-discuss] A Multi-Monitor Question
To: Alexander Roalter alexander@...
Cc: linuxwacom-discuss@...
Message-ID:
	167e8a330911181938m4552913ev87426bb21900409b@...
Content-Type: text/plain; charset="iso-8859-1"

Please see my comments in line.

Ping

On Wed, Nov 18, 2009 at 2:46 PM, Alexander Roalter alexander@...wrote:

After a long delay, I was finally able to update my X and other things,
and after removing a superfluous twinview option I forgot in the
keyboard section of the xorg.conf, I now can use the tablet (Graphire4),
and with xsetwacom set Stylus0 Screen_No n set it to different monitors.

I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
desktop.

If I though start the gimp or inkscape and use the XInput capabilities,
I get the ordinary mouse arrow right where it belongs, but the drawing
is done as if the entire desktop was used (therefore drawing a perfect
circle on the tablet, I get an ellipse which is three times as wide as
it is high.


Did you try the "KeepShape" option.  The problem is that your tablet has a
different width and height ration with your screen. If you use KeepShape,
don't forget your other mappings, such as topX/Y and bottomX/Y will not work
any more.

I have set the XInput mode to Screen. Setting it to Disable works as
expected (though of course I don't have any pressure sensitivity), and
setting it to Window also works almost as expected ... though I don't
know for sure, since I really don't know how that should behave... at
least there is no stretching in x-direction as is the case with the
Screen mode.


I don't have much knowledge about the Window v.s Screen mode either.  That's
a question for Gimp developers.

Any suggestions I should try with the configuration?

some infos from /var/log/Xorg.0.log:


(**) Stylus0: always reports core events
(**) Stylus0 device is /dev/input/wacom
(**) Stylus0 is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) Stylus0: reading USB link
(**) Option "ScreenNo" "0"
(**) Stylus0: attached screen number 0
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "Stylus0" (type: Wacom Stylus)
(**) Option "Device" "/dev/input/wacom"
Stylus0 Wacom X driver grabbed event device
(==) Wacom using pressure threshold of 30 for button 1
(==) Wacom USB Graphire4 tablet speed=9600 (38400) maxX=16704 maxY=12064
maxZ=51
1 resX=2032 resY=2032  tilt=disabled
(==) Wacom device "Stylus0" top X=0 top Y=0 bottom X=16704 bottom
Y=12064 resol
X=2032 resol Y=2032
(**) Option "SendCoreEvents"
(**) Eraser0: always reports core events
(**) Eraser0 device is /dev/input/wacom
(**) Eraser0 is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) Eraser0: reading USB link
(**) Option "ScreenNo" "0"
(**) Eraser0: attached screen number 0
(**) Eraser0: threshold = 30
(**) Eraser0: max x set to 16704 by xorg.conf
(**) Eraser0: max y set to 12064 by xorg.conf
(**) Eraser0: max z = 511
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "Eraser0" (type: Wacom Eraser)
(==) Wacom device "Eraser0" top X=0 top Y=0 bottom X=16704 bottom
Y=12064 resol X=2032 resol Y=2032
(**) Option "SendCoreEvents"
(**) Pad0: always reports core events
(**) Pad0 device is /dev/input/wacom
(**) Pad0 is in relative mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) Pad0: reading USB link
(**) Pad0: threshold = 30
(**) Pad0: max x set to 16704 by xorg.conf
(**) Pad0: max y set to 12064 by xorg.conf
(**) Pad0: max z = 511
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "Pad0" (type: Wacom Pad)
(==) Wacom device "Pad0" top X=0 top Y=0 bottom X=16704 bottom Y=12064
resol X=2032 resol Y=2032

Of course there is another set of devices already configured (my system
is OpenSuse 11.2), where the devices "Wacom Graphire4 6x8", "Wacom
Graphire4 6x8 cursor", "Wacom Graphire4 6x8 pad" and "Wacom Graphire4
6x8 eraser" are all already present, but I cannot set the automatically
in the xorg.conf to initial Screen_No 0 (perhaps that's not needed..)


Which linuxwacom are you running?  0.8.5-4 removes the duplicated devices
for you automatically.  Any version older than that will give you two sets
of devices if you have one defined in your xorg.conf.  You could disable the
hotplugging one by modifying the wacom fdi file under
/local/share/hal/fdi/policy/20thirdparty (10-linuxwacom.fdi on Fedora.  I am
not exactly sure where the file is located on your platform.  The name could
be different too.).

The Thing is: removing my definitions from the xorg.conf, I still get a
workable cursor, but it spans over the entire desktop, that is, in the
first third of the tablet I get the first third of the first monitor, in
the 2nd third of the tablet I get the second third of the second
monitor, etc.


HAL did the work for you.  You can add your options in the fdi file, or
disable fdi and add your device to xorg.conf, or update your wacom_drv.so to
0.8.5-4.  This is the beauty of open source - you have options :).

Monitors:
+------------++------------++---------------+
|111         ||    222     ||           3333|
|111         ||    222     ||           3333|
|111         ||    222     ||           3333|
+------------++------------++_______________+

Tablet    +-----+
         |1|2|3|
         +-----+

each part of the tablet maps to the corresponding field on the
corresponding monitor...  (which is bad)

So I'm with my self-defined xorg.conf:

Section "ServerLayout"
   Identifier     "Layout0"
   Screen      0  "Screen0" 0 0
   Screen      1  "Screen1" 1680 0
   Screen      2  "Screen2" 3360 0
   InputDevice    "Keyboard0" "CoreKeyboard"
   InputDevice    "Mouse0" "CorePointer"
   InputDevice    "Stylus0" "SendCoreEvents"
   InputDevice    "Eraser0" "SendCoreEvents"
   InputDevice    "Pad0" "SendCoreEvents"
EndSection


Section "InputDevice"
   Identifier     "Stylus0"
   Driver         "wacom"
   Option         "Device" "/dev/input/wacom"
   Option         "Type" "stylus"
   Option         "USB" "on"
   Option         "Screen_No" "0"
EndSection

Section "InputDevice"
   Identifier     "Eraser0"
   Driver         "wacom"
   Option         "Device" "/dev/input/wacom"
   Option         "Type" "eraser"
   Option         "USB" "on"
   Option         "Screen_No" "0"
EndSection

Section "InputDevice"
   Identifier     "Pad0"
   Driver         "wacom"
   Option         "Device" "/dev/input/wacom"
   Option         "Type" "pad"
   Option         "USB" "on"
EndSection


And I don't see where I can change the behavior for the XInput, so that
even in screen mode it works correctly and takes the width of the
current screen, and not the combined width.


--
Cheers,
Alex

-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 3
Date: Thu, 19 Nov 2009 22:03:46 +0100
From: Alexander Roalter alexander@...
Subject: Re: [Linuxwacom-discuss] A Multi-Monitor Question
To: Ping pinglinux@...
Cc: linuxwacom-discuss@...
Message-ID: 4B05B2B2.8020300@...
Content-Type: text/plain; charset=ISO-8859-1

On 11/19/2009 04:38 AM, Ping wrote:

Please see my comments in line.

Ping

On Wed, Nov 18, 2009 at 2:46 PM, Alexander Roalter <alexander@...
alexander@...> wrote:

    After a long delay, I was finally able to update my X and other things,
    and after removing a superfluous twinview option I forgot in the
    keyboard section of the xorg.conf, I now can use the tablet (Graphire4),
    and with xsetwacom set Stylus0 Screen_No n set it to different monitors.

    I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
    desktop.

    If I though start the gimp or inkscape and use the XInput capabilities,
    I get the ordinary mouse arrow right where it belongs, but the drawing
    is done as if the entire desktop was used (therefore drawing a perfect
    circle on the tablet, I get an ellipse which is three times as wide as
    it is high.


Did you try the "KeepShape" option.  The problem is that your tablet has
a different width and height ration with your screen. If you use
KeepShape, don't forget your other mappings, such as topX/Y and
bottomX/Y will not work any more.


Ok, tested that and it was worse than before, since only a tiny fraction
of the tablet is used anymore, and the behavior in x-direction remains
the same, in y direction now I can only paint on roughly 1/3rd of the
height -> even more distortion.

Which linuxwacom are you running?  0.8.5-4 removes the duplicated
devices for you automatically.  Any version older than that will give
you two sets of devices if you have one defined in your xorg.conf.  You
could disable the hotplugging one by modifying the wacom fdi file under
/local/share/hal/fdi/policy/20thirdparty (10-linuxwacom.fdi on Fedora. 
I am not exactly sure where the file is located on your platform.  The
name could be different too.).


Tried now 0.8.5-4, with kernel module also, still the same results.

I removed the fdi file and am now working with my self-set up files in
/etc/X11/xorg.conf (Stylus0, Eraser0, Pad0); Still, a device "Wacom
Graphire4 6x8" (without " pad", " eraser" or " cursor" extension added
=> before I had 4 of these devices, and I don't know where this device
is specified) is in the list, but there's no problem (apparently) with
it, so simply don't use it.

Since the cursor is displayed always on the correct position (but the
arrows on inkscape's rulers don't), I assume this is probably an X
error/problem. xidump displays values from 0 to 16000 (roughly), and I'm
not sure who does the computing for the output into the different input
streams =>

Does X11 receive only one data stream from the driver containing the
absolute coordinates (0-16000 in both directions, together with
pressure, tilt etc), or does X11 receive both the exact data (XInput?)
as well as preprocessed data it uses when not in XInput mode, which then
is used to place the normal cursor? At least that's what I think is
happening here:


driver =====Normal Input Channel =====> X11 (delivers coordinates from
					0 to 1680, 0 to 1050 as well as
                                        pressed buttons when in absolute
                                        mode, -1..+1 in both directions
                                        when in relative mode.

driver =====XInput Channel ==========> X11 (delivers coordinates from
                                        0 to 16384, 0 to 16384 and
                                       pressure and tilt and whatever
                                        else to X11.

or is it different, and the XInput Channel already gets again data from
0 to 1680 (or erroneously from 0 to 5280) to X11? If this is the case,
then it probably is a driver problem, but if X gets the original data
and does the computing by itself, then it's clearly an X problem (or the
Wacom driver for X, if any)

Re: A Multi-Monitor Question

2009-11-19T13:16:41Z

On 11/19/2009 10:03 PM, Alexander Roalter wrote:

> On 11/19/2009 04:38 AM, Ping wrote:
>> Please see my comments in line.
>>
>> Ping
>>
>> On Wed, Nov 18, 2009 at 2:46 PM, Alexander Roalter <alexander@...
>> <mailto:alexander@...>> wrote:
>>
>> After a long delay, I was finally able to update my X and other things,
>> and after removing a superfluous twinview option I forgot in the
>> keyboard section of the xorg.conf, I now can use the tablet (Graphire4),
>> and with xsetwacom set Stylus0 Screen_No n set it to different monitors.
>>
>> I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
>> desktop.
>>
>> If I though start the gimp or inkscape and use the XInput capabilities,
>> I get the ordinary mouse arrow right where it belongs, but the drawing
>> is done as if the entire desktop was used (therefore drawing a perfect
>> circle on the tablet, I get an ellipse which is three times as wide as
>> it is high.
>>
>>
>> Did you try the "KeepShape" option. The problem is that your tablet has
>> a different width and height ration with your screen. If you use
>> KeepShape, don't forget your other mappings, such as topX/Y and
>> bottomX/Y will not work any more.
>
> Ok, tested that and it was worse than before, since only a tiny fraction
> of the tablet is used anymore, and the behavior in x-direction remains
> the same, in y direction now I can only paint on roughly 1/3rd of the
> height -> even more distortion.
>
>>
>>
>> Which linuxwacom are you running? 0.8.5-4 removes the duplicated
>> devices for you automatically. Any version older than that will give
>> you two sets of devices if you have one defined in your xorg.conf. You
>> could disable the hotplugging one by modifying the wacom fdi file under
>> /local/share/hal/fdi/policy/20thirdparty (10-linuxwacom.fdi on Fedora.
>> I am not exactly sure where the file is located on your platform. The
>> name could be different too.).
>
> Tried now 0.8.5-4, with kernel module also, still the same results.
>
> I removed the fdi file and am now working with my self-set up files in
> /etc/X11/xorg.conf (Stylus0, Eraser0, Pad0); Still, a device "Wacom
> Graphire4 6x8" (without " pad", " eraser" or " cursor" extension added
> => before I had 4 of these devices, and I don't know where this device
> is specified) is in the list, but there's no problem (apparently) with
> it, so simply don't use it.
>
> Since the cursor is displayed always on the correct position (but the
> arrows on inkscape's rulers don't), I assume this is probably an X
> error/problem. xidump displays values from 0 to 16000 (roughly), and I'm
> not sure who does the computing for the output into the different input
> streams =>
>
> Does X11 receive only one data stream from the driver containing the
> absolute coordinates (0-16000 in both directions, together with
> pressure, tilt etc), or does X11 receive both the exact data (XInput?)
> as well as preprocessed data it uses when not in XInput mode, which then
> is used to place the normal cursor? At least that's what I think is
> happening here:
>
>
> driver =====Normal Input Channel =====> X11 (delivers coordinates from
> 0 to 1680, 0 to 1050 as well as
> pressed buttons when in absolute
> mode, -1..+1 in both directions
> when in relative mode.
>
> driver =====XInput Channel ==========> X11 (delivers coordinates from
> 0 to 16384, 0 to 16384 and
> pressure and tilt and whatever
> else to X11.
>
> or is it different, and the XInput Channel already gets again data from
> 0 to 1680 (or erroneously from 0 to 5280) to X11? If this is the case,
> then it probably is a driver problem, but if X gets the original data
> and does the computing by itself, then it's clearly an X problem (or the
> Wacom driver for X, if any)
>

Hm, it can also be a GTK problem (i don't have any non-gtk XInput aware
apps), so this thread might help (and keep the blame off the wacom driver):

http://www.gimpusers.com/forums/gimp-developer/10806-xinerama-and-wacom.html

--
Cheers,
Alex

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: A Multi-Monitor Question

2009-11-19T13:03:46Z

On 11/19/2009 04:38 AM, Ping wrote:

> Please see my comments in line.
>
> Ping
>
> On Wed, Nov 18, 2009 at 2:46 PM, Alexander Roalter <alexander@...
> <mailto:alexander@...>> wrote:
>
> After a long delay, I was finally able to update my X and other things,
> and after removing a superfluous twinview option I forgot in the
> keyboard section of the xorg.conf, I now can use the tablet (Graphire4),
> and with xsetwacom set Stylus0 Screen_No n set it to different monitors.
>
> I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
> desktop.
>
> If I though start the gimp or inkscape and use the XInput capabilities,
> I get the ordinary mouse arrow right where it belongs, but the drawing
> is done as if the entire desktop was used (therefore drawing a perfect
> circle on the tablet, I get an ellipse which is three times as wide as
> it is high.
>
>
> Did you try the "KeepShape" option. The problem is that your tablet has
> a different width and height ration with your screen. If you use
> KeepShape, don't forget your other mappings, such as topX/Y and
> bottomX/Y will not work any more.

Ok, tested that and it was worse than before, since only a tiny fraction
of the tablet is used anymore, and the behavior in x-direction remains
the same, in y direction now I can only paint on roughly 1/3rd of the
height -> even more distortion.

>
>
> Which linuxwacom are you running? 0.8.5-4 removes the duplicated
> devices for you automatically. Any version older than that will give
> you two sets of devices if you have one defined in your xorg.conf. You
> could disable the hotplugging one by modifying the wacom fdi file under
> /local/share/hal/fdi/policy/20thirdparty (10-linuxwacom.fdi on Fedora.
> I am not exactly sure where the file is located on your platform. The
> name could be different too.).

Tried now 0.8.5-4, with kernel module also, still the same results.

I removed the fdi file and am now working with my self-set up files in
/etc/X11/xorg.conf (Stylus0, Eraser0, Pad0); Still, a device "Wacom
Graphire4 6x8" (without " pad", " eraser" or " cursor" extension added
=> before I had 4 of these devices, and I don't know where this device
is specified) is in the list, but there's no problem (apparently) with
it, so simply don't use it.

Since the cursor is displayed always on the correct position (but the
arrows on inkscape's rulers don't), I assume this is probably an X
error/problem. xidump displays values from 0 to 16000 (roughly), and I'm
not sure who does the computing for the output into the different input
streams =>

Does X11 receive only one data stream from the driver containing the
absolute coordinates (0-16000 in both directions, together with
pressure, tilt etc), or does X11 receive both the exact data (XInput?)
as well as preprocessed data it uses when not in XInput mode, which then
is used to place the normal cursor? At least that's what I think is
happening here:

driver =====Normal Input Channel =====> X11 (delivers coordinates from
0 to 1680, 0 to 1050 as well as
pressed buttons when in absolute
mode, -1..+1 in both directions
when in relative mode.

driver =====XInput Channel ==========> X11 (delivers coordinates from
0 to 16384, 0 to 16384 and
pressure and tilt and whatever
else to X11.

or is it different, and the XInput Channel already gets again data from
0 to 1680 (or erroneously from 0 to 5280) to X11? If this is the case,
then it probably is a driver problem, but if X gets the original data
and does the computing by itself, then it's clearly an X problem (or the
Wacom driver for X, if any)

--
Cheers,
Alex

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: A Multi-Monitor Question

2009-11-18T19:38:50Z

Please see my comments in line.

Ping

On Wed, Nov 18, 2009 at 2:46 PM, Alexander Roalter <alexander@...> wrote:

After a long delay, I was finally able to update my X and other things,
and after removing a superfluous twinview option I forgot in the
keyboard section of the xorg.conf, I now can use the tablet (Graphire4),
and with xsetwacom set Stylus0 Screen_No n set it to different monitors.

I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
desktop.

If I though start the gimp or inkscape and use the XInput capabilities,
I get the ordinary mouse arrow right where it belongs, but the drawing
is done as if the entire desktop was used (therefore drawing a perfect
circle on the tablet, I get an ellipse which is three times as wide as
it is high.

Did you try the "KeepShape" option. The problem is that your tablet has a different width and height ration with your screen. If you use KeepShape, don't forget your other mappings, such as topX/Y and bottomX/Y will not work any more.

I have set the XInput mode to Screen. Setting it to Disable works as
expected (though of course I don't have any pressure sensitivity), and
setting it to Window also works almost as expected ... though I don't
know for sure, since I really don't know how that should behave... at
least there is no stretching in x-direction as is the case with the
Screen mode.

I don't have much knowledge about the Window v.s Screen mode either. That's a question for Gimp developers.

Any suggestions I should try with the configuration?

some infos from /var/log/Xorg.0.log:

(**) Stylus0: always reports core events
(**) Stylus0 device is /dev/input/wacom
(**) Stylus0 is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) Stylus0: reading USB link
(**) Option "ScreenNo" "0"
(**) Stylus0: attached screen number 0
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "Stylus0" (type: Wacom Stylus)
(**) Option "Device" "/dev/input/wacom"
Stylus0 Wacom X driver grabbed event device
(==) Wacom using pressure threshold of 30 for button 1
(==) Wacom USB Graphire4 tablet speed=9600 (38400) maxX=16704 maxY=12064
maxZ=51
1 resX=2032 resY=2032 tilt=disabled
(==) Wacom device "Stylus0" top X=0 top Y=0 bottom X=16704 bottom
Y=12064 resol
X=2032 resol Y=2032
(**) Option "SendCoreEvents"
(**) Eraser0: always reports core events
(**) Eraser0 device is /dev/input/wacom
(**) Eraser0 is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) Eraser0: reading USB link
(**) Option "ScreenNo" "0"
(**) Eraser0: attached screen number 0
(**) Eraser0: threshold = 30
(**) Eraser0: max x set to 16704 by xorg.conf
(**) Eraser0: max y set to 12064 by xorg.conf
(**) Eraser0: max z = 511
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "Eraser0" (type: Wacom Eraser)
(==) Wacom device "Eraser0" top X=0 top Y=0 bottom X=16704 bottom
Y=12064 resol X=2032 resol Y=2032
(**) Option "SendCoreEvents"
(**) Pad0: always reports core events
(**) Pad0 device is /dev/input/wacom
(**) Pad0 is in relative mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) Pad0: reading USB link
(**) Pad0: threshold = 30
(**) Pad0: max x set to 16704 by xorg.conf
(**) Pad0: max y set to 12064 by xorg.conf
(**) Pad0: max z = 511
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "Pad0" (type: Wacom Pad)
(==) Wacom device "Pad0" top X=0 top Y=0 bottom X=16704 bottom Y=12064
resol X=2032 resol Y=2032

Of course there is another set of devices already configured (my system
is OpenSuse 11.2), where the devices "Wacom Graphire4 6x8", "Wacom
Graphire4 6x8 cursor", "Wacom Graphire4 6x8 pad" and "Wacom Graphire4
6x8 eraser" are all already present, but I cannot set the automatically
in the xorg.conf to initial Screen_No 0 (perhaps that's not needed..)

Which linuxwacom are you running? 0.8.5-4 removes the duplicated devices for you automatically. Any version older than that will give you two sets of devices if you have one defined in your xorg.conf. You could disable the hotplugging one by modifying the wacom fdi file under /local/share/hal/fdi/policy/20thirdparty (10-linuxwacom.fdi on Fedora. I am not exactly sure where the file is located on your platform. The name could be different too.).

The Thing is: removing my definitions from the xorg.conf, I still get a
workable cursor, but it spans over the entire desktop, that is, in the
first third of the tablet I get the first third of the first monitor, in
the 2nd third of the tablet I get the second third of the second
monitor, etc.

HAL did the work for you. You can add your options in the fdi file, or disable fdi and add your device to xorg.conf, or update your wacom_drv.so to 0.8.5-4. This is the beauty of open source - you have options :).

Monitors:
+------------++------------++---------------+
|111 || 222 || 3333|
|111 || 222 || 3333|
|111 || 222 || 3333|
+------------++------------++_______________+

Tablet +-----+
|1|2|3|
+-----+

each part of the tablet maps to the corresponding field on the
corresponding monitor... (which is bad)

So I'm with my self-defined xorg.conf:

Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" 1680 0
Screen 2 "Screen2" 3360 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
InputDevice "Stylus0" "SendCoreEvents"
InputDevice "Eraser0" "SendCoreEvents"
InputDevice "Pad0" "SendCoreEvents"
EndSection

Section "InputDevice"
Identifier "Stylus0"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on"
Option "Screen_No" "0"
EndSection

Section "InputDevice"
Identifier "Eraser0"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "USB" "on"
Option "Screen_No" "0"
EndSection

Section "InputDevice"
Identifier "Pad0"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "pad"
Option "USB" "on"
EndSection

And I don't see where I can change the behavior for the XInput, so that
even in screen mode it works correctly and takes the width of the
current screen, and not the combined width.

--
Cheers,
Alex

Re: A Multi-Monitor Question

2009-11-18T19:17:00Z

On Wed, Nov 18, 2009 at 8:29 PM, Eric Honaker
<songwindapogee@...> wrote:
>
> I have wondered about that, actually. Doesn't the Cintiq act like an extra monitor? Wouldn't the issue be the same?
>
> Or are you thinking you would just run your Cintiq in "clone" mode?
>

No, actually I'd run the Cintiq side-by-side as it does pipe VGA into
the screen under the tablet. I just got to find that normal (not
wide-screen) one that does 1600x1200, which will match the height of
the 1920x1200 screen. That way, I can run twinview on the NVidia
card.

> Kelly Price wrote:
>
> On Wed, Nov 18, 2009 at 5:46 PM, Alexander Roalter <alexander@...> wrote:
>
>
> I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
> desktop.
>
>
>
> (snip)
>
>
> The Thing is: removing my definitions from the xorg.conf, I still get a
> workable cursor, but it spans over the entire desktop, that is, in the
> first third of the tablet I get the first third of the first monitor, in
> the 2nd third of the tablet I get the second third of the second
> monitor, etc.
>
> Monitors:
> +------------++------------++---------------+
> |111 || 222 || 3333|
> |111 || 222 || 3333|
> |111 || 222 || 3333|
> +------------++------------++_______________+
>
> Tablet +-----+
> |1|2|3|
> +-----+
>
> each part of the tablet maps to the corresponding field on the
> corresponding monitor... (which is bad)
>
>
>
> (snip)
>
>
> And I don't see where I can change the behavior for the XInput, so that
> even in screen mode it works correctly and takes the width of the
> current screen, and not the combined width.
>
>
>
> I had the same problem, with a similar setup (two monitor, similar to
> your #2/#3 setup). I disabled screen mode in Gimp and made sure the
> Xwindows config was sane in order to get the Graphire4 I have working
> properly. Now if I can get it to a setup I can use and works with KDE
> 4.x, all will be well. Unfortunately, KDE 4 doesn't play nice with
> multiscreen (as seperate X screens) setups.
>
> I might as well save up for a Cintque.
>
>
>
> --
> Eric Honaker
> Dragonsept Arts and Publishing
> PGP Public Key: F1BC60E6
> "Words are, of course, the most powerful drug used by mankind." -- Rudyard Kipling

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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: A Multi-Monitor Question

2009-11-18T17:29:01Z

I have wondered about that, actually. Doesn't the Cintiq act like an extra monitor? Wouldn't the issue be the same?

Or are you thinking you would just run your Cintiq in "clone" mode?

Kelly Price wrote:

On Wed, Nov 18, 2009 at 5:46 PM, Alexander Roalter alexander@... wrote:

I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
desktop.

(snip)

The Thing is: removing my definitions from the xorg.conf, I still get a
workable cursor, but it spans over the entire desktop, that is, in the
first third of the tablet I get the first third of the first monitor, in
the 2nd third of the tablet I get the second third of the second
monitor, etc.

Monitors:
+------------++------------++---------------+
|111         ||    222     ||           3333|
|111         ||    222     ||           3333|
|111         ||    222     ||           3333|
+------------++------------++_______________+

Tablet    +-----+
         |1|2|3|
         +-----+

each part of the tablet maps to the corresponding field on the
corresponding monitor...  (which is bad)

(snip)

And I don't see where I can change the behavior for the XInput, so that
even in screen mode it works correctly and takes the width of the
current screen, and not the combined width.


I had the same problem, with a similar setup (two monitor, similar to
your #2/#3 setup).  I disabled screen mode in Gimp and made sure the
Xwindows config was sane in order to get the Graphire4 I have working
properly.  Now if I can get it to a setup I can use and works with KDE
4.x, all will be well.  Unfortunately, KDE 4 doesn't play nice with
multiscreen (as seperate X screens) setups.

I might as well save up for a Cintque.

--
Eric Honaker
Dragonsept Arts and Publishing
PGP Public Key: F1BC60E6
"Words are, of course, the most powerful drug used by mankind." -- Rudyard Kipling

Re: A Multi-Monitor Question

2009-11-18T15:47:29Z

On Wed, Nov 18, 2009 at 5:46 PM, Alexander Roalter <alexander@...> wrote:
> I have three monitors side-by-side on a 1680+1680+1920 by 1080 large
> desktop.
>
(snip)

> The Thing is: removing my definitions from the xorg.conf, I still get a
> workable cursor, but it spans over the entire desktop, that is, in the
> first third of the tablet I get the first third of the first monitor, in
> the 2nd third of the tablet I get the second third of the second
> monitor, etc.
>
> Monitors:
> +------------++------------++---------------+
> |111 || 222 || 3333|
> |111 || 222 || 3333|
> |111 || 222 || 3333|
> +------------++------------++_______________+
>
> Tablet +-----+
> |1|2|3|
> +-----+
>
> each part of the tablet maps to the corresponding field on the
> corresponding monitor... (which is bad)
>

(snip)
>
> And I don't see where I can change the behavior for the XInput, so that
> even in screen mode it works correctly and takes the width of the
> current screen, and not the combined width.
>

I had the same problem, with a similar setup (two monitor, similar to
your #2/#3 setup). I disabled screen mode in Gimp and made sure the
Xwindows config was sane in order to get the Graphire4 I have working
properly. Now if I can get it to a setup I can use and works with KDE
4.x, all will be well. Unfortunately, KDE 4 doesn't play nice with
multiscreen (as seperate X screens) setups.

I might as well save up for a Cintque.

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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss