How to limit pen tablet to one display out of two?

[1script]

Hi all, this task got me scratchin' my head hard now knowing where to start, so any idea that may push me in the right direction will be greatly appreciated.

I'm running a

Release 10.04(lucid)
Kernel Linux 2.6.32-24-generic
GNOME 2.30.2

Using NVIDIA Driver Version 195.36.24 with two monitors 1280x1024 each in TwinView configuration

My Pen tablet is ID 5543:0005 UC-Logic Technology Corp. Genius MousePen 8x6 Tablet, Wizardpen driver (not sure how to lookup its version)

The tablet is currently working just fine except for this one thing I'm trying to fix: it now covers the entire 2560 pixel width of the desktop and 1024 pixel height. Given that the tablet itself has a 4x3 side ratio, it results in its horizontal resolution being half of the vertical one. Basically, when you use it to draw anything you always have to mentally correct what you do by limiting your horizontal movements to only half of vertical ones which makes drawing a (relatively) straight line an impossible task.

So, this got me thinking that I want to make sure the tablet only works on one of the two displays - the one I'd open Gimp and Inkscape on - the only two programs I ever use the tablet with. However, when I look at the calibration settings of the tablet itself, it only allows me to limit the area of the tablet I want to be sensitive, not the area of display. I cannot find any such settings in NVIDIA X Server Settings either although I think this is where it might have been.

So, does anyone know how to leave the same size of the tablet drawing area but make it move the cursor only on one particular monitor in TwinView configuration?

Thank you for all your suggestions!

[shadarack]

I have the same issue, but with a genius pensketch 9x12 and a 3200x900 display. No clue how to limit it to one monitor, but would a possible workaround be to change the area of the tablet that is sensitive to match the dimensions of your desktop? This would mean giving up a big chunk of your tablet, but would at least make it usable, yes?

Only problem is, I have no clue how to do that. I followed the tutorial here to get my tablet working:

https://help.ubuntu.com/community/TabletSetupWizardpen

but bzr is not working for me for some reason - I suspect a server may be down, so I cannot install the calibration tool. No clue how to manually configure xorg.conf to calibrate my tablet properly without it.

[Favux]

Hi shadarack,

I don't know either. Maybe we can figure it out. Enter in a terminal:

xinput --list

and then post its output. Then using the "Device name" it uses for your stylus let's look at:

xinput list-props "Device name"

using the quotes around the Device name and post its output. Let's see if we can use xinput to set or map to the screen.

[shadarack]

Ack! I was so not expecting such a swift response! Here you go:

xinput --list results in:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳                 9x12 Tablet             	id=10	[slave  pointer  (2)]
⎜   ↳                 9x12 Tablet             	id=11	[slave  pointer  (2)]
⎜   ↳                 9x12 Tablet             	id=12	[slave  pointer  (2)]
⎜   ↳ ImPS/2 Logitech Wheel Mouse             	id=13	[slave  pointer  (2)]
⎜   ↳ Macintosh mouse button emulation        	id=14	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳   USB Keyboard                          	id=8	[slave  keyboard (3)]
    ↳   USB Keyboard                          	id=9	[slave  keyboard (3)]

xinput list-props "                 9x12 Tablet" gives me:

Device '                9x12 Tablet':
	Device Enabled (121):	1
	Device Accel Profile (242):	0
	Device Accel Constant Deceleration (243):	1.000000
	Device Accel Adaptive Deceleration (245):	1.000000
	Device Accel Velocity Scaling (246):	10.000000
	Evdev Reopen Attempts (236):	10
	Evdev Axis Inversion (247):	0, 0
	Evdev Axis Calibration (248):	<no items>
	Evdev Axes Swap (249):	0
	Axis Labels (250):	"Abs X" (239), "Abs Y" (240), "Abs Pressure" (241)
	Button Labels (251):	"Button 0" (238), "Button Unknown" (237), "Button Unknown" (237), "Button Wheel Up" (125), "Button Wheel Down" (126)
	Evdev Middle Button Emulation (252):	2
	Evdev Middle Button Timeout (253):	50
	Evdev Wheel Emulation (254):	0
	Evdev Wheel Emulation Axes (255):	0, 0, 4, 5
	Evdev Wheel Emulation Inertia (256):	10
	Evdev Wheel Emulation Timeout (257):	200
	Evdev Wheel Emulation Button (258):	4
	Evdev Drag Lock Buttons (259):	0

[Favux]

Hi Hi shadarack,

Doesn't look like much to work with. What is your video chipset?:

lspci | grep VGA

and what video driver are you using? Did it add entries into the xorg.conf in /etc/X11?

But first we need to take a step back. The list-props seems to indicated that your tablet is on the evdev failsafe driver, not WizardPen. So let's deal with that first. What is your tablet line look like from?:

lsusb

[shadarack]

My video chipset is Nvidia. Specifically:

01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8500 GT] (rev a1)

If it makes any sort of difference, I'm running a dual monitor setup at 3200 x 900 resolution, twinview.

As for the Wizardpen driver, I'm actually rather surprised at that. I did follow a tutorial that had me install the drivers. I was not aware that Ubuntu had incorporated any sort of default working drivers for tablets! Last time I tried to install a tablet(a few years ago, also a wizardpen tablet), it didn't work until I had working drivers for it. Regardless, lsusb gives this return:

Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 5543:0042 UC-Logic Technology Corp. Tablet PF1209
Bus 004 Device 002: ID 04d9:1603 Holtek Semiconductor, Inc. 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Favux]

Are you using the Nvidia proprietary drivers?

Alright, it's a UC-Logic tablet. What WizardPen driver did you install and how? Also we should take a look at your 70-wizardpen.conf at /usr/lib/X11/xorg.conf.d/. Please post it.

[SnickerSnack]

I am having the same issue with a wacom based tablet. I can make a new thread or wait my turn in this one if that's better.

Here's my info:

zsharon@Weierstrass:~$ xinput --list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Serial Wacom Tablet eraser              	id=13	[slave  pointer  (2)]
⎜   ↳ Serial Wacom Tablet                     	id=14	[slave  pointer  (2)]
⎜   ↳ Macintosh mouse button emulation        	id=15	[slave  pointer  (2)]
⎜   ↳ Logitech USB Gaming Mouse               	id=9	[slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                   	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=10	[slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                  	id=12	[slave  keyboard (3)]

zsharon@Weierstrass:~$ xinput list-props "Serial Wacom Tablet"
Device 'Serial Wacom Tablet':
	Device Enabled (135):	1
	Device Accel Profile (257):	0
	Device Accel Constant Deceleration (258):	1.000000
	Device Accel Adaptive Deceleration (260):	1.000000
	Device Accel Velocity Scaling (261):	10.000000
	Wacom Tablet Area (282):	0, 0, 24576, 18432
	Wacom Rotation (283):	0
	Wacom Pressurecurve (284):	0, 0, 100, 100
	Wacom Serial IDs (285):	144, 0, 2, 0
	Wacom TwinView Resolution (286):	0, 0, 0, 0
	Wacom Display Options (287):	-1, 0, 1
	Wacom Screen Area (288):	0, 0, 1024, 768
	Wacom Proximity Threshold (289):	0
	Wacom Capacity (290):	-1
	Wacom Pressure Threshold (291):	7
	Wacom Sample and Suppress (292):	2, 4
	Wacom Enable Touch (293):	0
	Wacom Hover Click (294):	1
	Wacom Tool Type (295):	"STYLUS" (297)
	Wacom Button Actions (296):	"None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0)

I can try some guesswork with these settings...

EDIT: Okay, I've pushed a few things around to regain some familiarity, but I'm not sure how to change only one of the settings in a list, like this one:

Wacom Screen Area (288): 0, 0, 1024, 768

I don't want to break anything, so I'm going to google around before trying...




EDIT: This might be useful

zsharon@Weierstrass:/usr/bin$ xsetwacom list param
.
.
.
.
mmonitor - Turns on/off across monitor movement in multi-monitor desktop, default is on

This didn't seem to work:

zsharon@Weierstrass:/usr/bin$ xsetwacom --set 13 mmonitor 0

[Favux]

Hi SnickerSnack, good to hear from you again,

Partly it depends on which release of Ubunutu you are in and what version of xf86-input-wacom.

The multimonitor support has been dropped with 0.10.9 xf86-input-wacom and up but we are given a new command:

xsetwacom set <device name> "MapToOutput" VGA1

As an example. You'd use the output device you want of course. So we should know your video chipset, driver, and xrandr output. I don't think we need to look at 'xrandr -q --verbose':

xrandr

The problem is with using it we've been getting an error. I think I may have figured out the problem.

So if you have updated past the default 0.10.8 in Maverick try the command and let's see what error you get.

If you are still with the default we can try some of the old xsetwacom commands. But the Xorg developer working on xf86-input-wacom was commenting that they were broken anyway as he dropped them. However some people were reporting being able to use them.

[SnickerSnack]

Hi SnickerSnack, good to hear from you again,

You too. I also stumbled on some of your comments here (link) as I'm having a bit of trouble with GIMP as well. I've just about nailed down an issue that I'll soon post a description of here to make sure I'm not overlooking something, and then I'll submit a bug report if needed.

Partly it depends on which release of Ubunutu you are in and what version of xf86-input-wacom.

I'm still using 10.04 Lucid and xserver-xorg-input-wacom 1:0.10.5-0ubuntu4. As far as I know, I don't have xf86-input-wacom installed. I should probably update, but I haven't taken the time to see whether doing so would break anything I've set up. Sigh...I guess it's time. I'll do that and see about this problem afterward.

Thanks.