GNOME Bugzilla – Bug 606240
Multiple cursors always have the same cursor for one window, has to do with the last cursor that moved
Last modified: 2010-07-12 07:56:22 UTC
I'm reporting this as a gtk problem because this bug does not occur in KDE 3 or KDE 4 applications, only in gnome ones. Unfortunately, I don't know weather it is gtk or gdk or what, so I took my best guess. The problem is that when Multiple MPX cursors are on the same gtk window, they are both the same, even if one was over text and another is over a button. Both cursors are set to the type that the last cursor that moved should be. To reproduce the bug: 0. Get MPX working. (You'll need Lucid, and extra mouse and keyboard, and this tutorial->http://alec.mooo.com/mpx.php. ) 1. Open a gtk application. Gedit for example. 2. Type some text. 3. Put cursor A over the text. 4. Put cursor B over a toolbar button (Without moving cursor A). 5. Notice that both cursors are a pointer. 6. Move cursor A the slightest bit. 7. Notice that both cursors are are the text, capital i-shaped style. What I expected instead:That each cursor would be the style associated with whatever it was over, independently of the other cursor. Please let me know if you need any more info. This bug was forwarded from https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/503632 . Version info: DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091228) Package: libgtk2.0-0 2.19.1-1 ProcEnviron: LC_CTYPE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 2.6.32-9.13-generic Uname: Linux 2.6.32-9-generic x86_64
I should correct the part that says you'll need Lucid (that only applies to Ubuntu). Instead you just need X11R7.5. Thanks for the great job you do.
You will probably have to wait for bug 596725 to be fixed in order to get proper MPX support in GTK+.
(In reply to comment #2) > You will probably have to wait for bug 596725 to be fixed in order to get > proper MPX support in GTK+. So is the bug I reported the same as bug 596725, or is bug 596725 just something that has to be fixed before you can really fix this bug? I'm asking mostly so I know weather to report any other bugs I find related to mpx on gtk.
Setting dependency
(In reply to comment #3) > So is the bug I reported the same as bug 596725, or is bug 596725 just > something that has to be fixed before you can really fix this bug? I'm asking > mostly so I know weather to report any other bugs I find related to mpx on gtk. using XInput2 (what bug #569725 is about) will have this bug fixed as a side-effect, amongst many others you'll find in the current state. Setting the GDK_NATIVE_WINDOWS envvar would make GTK+ behave exactly like KDE regarding this (since every GdkWindow would have a matching X Window, what X expects), but I wouldn't recommend this at all.
Hrm, sorry, bug #596725
I assume this is fixed now that we have xinput2 support.
Thanks! When do you think that this will be in ubuntu so I can test it?
(In reply to comment #8) > Thanks! When do you think that this will be in ubuntu so I can test it? Up to Ubuntu. Please ask Ubuntu instead.