After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 324913 - Stylus tablet does not work across multiple monitors
Stylus tablet does not work across multiple monitors
Status: RESOLVED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
2.8.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 609086 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-12-24 03:16 UTC by buttknock1
Modified: 2015-06-13 17:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description buttknock1 2005-12-24 03:16:51 UTC
Please describe the problem:
I reported this bug for the windows port but it seems it still remains for the
Linux port of GTK+ when I use the GIMP the cursor does not follow the pointer
properly.  Please read this bug link for details:
http://bugzilla.gnome.org/show_bug.cgi?id=145467

There is a solution for the windows port hopefully will work or help towards
fixing this bug in the Linux version.

Steps to reproduce:
1. Using the GIMP with 2 or 3 monitors and a stylus (I used a Calcomp)
2. Go to preferences and Input Devices, Configure Extended Input Devices
3. Change the Mode to Screen, save it, cursor offsets itself as it moves across
an image that is being worked on.


Actual results:
Stylus tablet cursor cannot move across 3 monitors, only 2 and the cursor is
offset when moved from left to right.  Only works on 2nd and 3rd monitor, the
cursor becomes more offset as the cursor moves from the 2nd monitor to the 3rd.
 The cursor cannot move to the 1st monitor at all.  

Expected results:
For the Cursor to follow the pointer and use pressure.

Does this happen every time?
yes

Other information:
Please read this bug report for more details into a possible solution
http://bugzilla.gnome.org/show_bug.cgi?id=145467
Comment 1 Michael Schumacher 2010-02-06 11:05:51 UTC
*** Bug 609086 has been marked as a duplicate of this bug. ***
Comment 2 Matthias Clasen 2014-01-24 23:24:17 UTC
Is this bug still relevant ? A lot has changed since 2005
Comment 3 Alexandre Franke 2015-06-13 17:24:51 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!