GNOME Bugzilla – Bug 457118
tablet problems when switching to/from fullscreen mode
Last modified: 2008-03-27 20:21:52 UTC
When switching to and from fullscreen mode, the cursor is offset from the point where any tool is actually used. (paint, marquee, blur, paths, etc. ) It goes like this: When the cursor is working properly in fullscreen mode, and I switch to windowed mode, the cursor is now offset to the upper-left by a few inches. When the cursor works properly in windowed mode, and I switch to fullscreen, the cursor is offset the same distance to the lower-right. To replicate this problem: Create or open a file. Press F11 to go to fullscreen. At that point it is apparent the cursor is in the wrong place. To get the cursor where it should be, I have to hover it over a menu, status bar, or other non-canvas surface, and then it is in the right position. This is a suitable solution for now. Note that if you use the Menu > View > Fullscreen button, the cursor will still be in the right place in fullscreen. This bug only happens when I use the F11 shortcut, or the ESC key to leave fullscreen mode. I see no reference to this problem anywhere, so it could be that somehow I screwed up things on my own side. So unless someone else can duplicate this I wouldn't bother looking for why its happening. Chris
I have never experienced this while running Linux or Solaris, so this is probably a Windows-specific problem. It would be nice if some other Windows users could try the F11 shortcut and maybe confirm this bug report.
I've never experienced this. Chris, what kind of input device do you use?
Comment #2 from Michael Schumacher (developer, points: 18) 2007-07-16 08:35 UTC [reply] I've never experienced this. Chris, what kind of input device do you use? ---------- I should have mentioned this! I use a Wacom Graphire 3 tablet driver 5.03-3 (most recent). I hadn't thought about trying my mouse instead to see if the problem remains. I just discovered that when I use my USB mouse, the cursor offset never happens. Also, I found that this offset only occurs when I plug in my tablet BEFORE starting GIMP (which is typical, I use my tablet for everything). If I plug in my tablet AFTER GIMP has started, there is no problem. Having realized this, for me this bug is easily avoided. It might be more of a problem if the USB was less accessible (I use a laptop). Also I use GTK+ version 2.10.13. By the way, I am very impressed with how fast the response is to this bug report! It's no wonder open source software is so reliable.
If you plug in the tablet after you started GIMP, it might just work as a core pointer (i.e. just like a normal mouse, no pressure sensitivity).
You're right. I just noticed that sensitivity / eraser are no longer recognized. I wonder if anyone else using WinXP and a tablet has the cursor problem too.
*** Bug 471345 has been marked as a duplicate of this bug. ***
I have to admit that rc2 has that problem. Apparently it hasn't been fixed yet.
I have exactly the same problem. I use Windows XP SP2. I have tested Gimp 2.2.13 2.2.15 and 2.2.17 and different versions of Gtk+ My tablet is a Genius mousepen with the most recent driver. The bug occurs when F11, but if you move the pointer with the mouse too. The tablet become unable to work because of offset. I have to close Gimp, because closing the drawing window doesn't work. The only mean for me is to start gimp with --ignore-wintab, or plug the tablet after Gimp started. Of course, no pressure for drawing... I have tested Gimp 2.4 rc3, and there is a little difference. There is no offset, and i have the pressure, but the mouse can no longer be used in the drawing area (selection, rules, right button, moving a layer...) after you send any event to gimp from the tablet. It's a portable version of gimp and gtk found in http://www.aljacom.com/~gimp/download.html Hope it can be usefull.
With Gimp 2.4.4 and his Gtk+, the bug exist... With Gimp 2.4.5 and his new Gtk+ (linked in the installer for windows), i have no more problems. All works fine !!! No offset, never. In my point of view, this bug can be closed.
Great. Closing this bug.