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 603849 - No mouse event with gtk-2.18.x
No mouse event with gtk-2.18.x
Status: RESOLVED DUPLICATE of bug 601473
Product: gtkglext
Classification: Other
Component: examples
unspecified
Other Linux
: Normal normal
: 2.0.0
Assigned To: Mukund Sivaraman
Mukund Sivaraman
Depends on:
Blocks:
 
 
Reported: 2009-12-05 15:52 UTC by Hiromasa Yoshimoto
Modified: 2010-01-12 18:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to shapes to fix this issue (761 bytes, patch)
2009-12-09 18:26 UTC, Mukund Sivaraman
none Details | Review
Updated patch to fix all affected example programs (3.56 KB, patch)
2009-12-09 20:01 UTC, Mukund Sivaraman
committed Details | Review
Button motion test program (2.08 KB, text/plain)
2009-12-11 04:05 UTC, Mukund Sivaraman
  Details

Description Hiromasa Yoshimoto 2009-12-05 15:52:52 UTC
When using gtk-2.18.x, the "shapes" demo can not receive mouse event at all.

This seems to be caused by client-side windows issue, and workarounded by GDK_NATIVE_WINDOWS environment;

$ GDK_NATIVE_WINDOWS=1 ./shapes
Comment 1 Mukund Sivaraman 2009-12-07 01:26:06 UTC
I am able to reproduce this issue too, and the suggested workaround works.
Comment 2 Mukund Sivaraman 2009-12-09 18:26:32 UTC
Created attachment 149468 [details] [review]
Patch to shapes to fix this issue

We seem to be fine with regards to the GTK+ client-side windows checklist:
http://library.gnome.org/devel/gtk/2.18/gtk-migrating-ClientSideWindows.html

It seems that the shapes example gets the button press and release events, but not the motion notify events. Setting the appropriate mask on the drawing area fixes this issue. It looks like the default behavior of receiving motion notify events has changed.

Patch to fix this issue is attached.
Comment 3 Mukund Sivaraman 2009-12-09 18:27:43 UTC
Removing csw keyword as it's not a client-side windows issue.
Comment 4 Mukund Sivaraman 2009-12-09 20:01:24 UTC
Created attachment 149476 [details] [review]
Updated patch to fix all affected example programs
Comment 5 Mukund Sivaraman 2009-12-09 20:04:29 UTC
Review of attachment 149476 [details] [review]:

Patch in comment #4 was committed to master branch in a912adadbac2a1cd0b00379d7ecec457f9505c05.
Comment 6 Mukund Sivaraman 2009-12-09 20:07:01 UTC
Resolving as FIXED, without any milestone as we don't have milestones configured yet.

hiromasa yoshimoto: Please verify that this bug is fixed in the master branch.
Comment 7 Mukund Sivaraman 2009-12-11 04:01:46 UTC
Reopening bug as using pointer motion mask means that events are very chatty, whereas we are only interested in button motion events.

Plus, button motion mask does work for ordinary GTK+ apps, so this seems something specific to gtkglext.
Comment 8 Mukund Sivaraman 2009-12-11 04:05:13 UTC
Created attachment 149561 [details]
Button motion test program

Simple testcase demonstrating that button motion events work properly in ordinary GTK+ apps. This testcase uses cairo to draw onto a GtkDrawingArea.
Comment 9 Mukund Sivaraman 2010-01-11 20:57:55 UTC
Setting milestone to 2.0.0.
Comment 10 Mukund Sivaraman 2010-01-12 18:08:19 UTC
This bug seems to be the same as bug #601473, and I verify that the bug no longer exists in gtk+ 2.18.5.

*** This bug has been marked as a duplicate of bug 601473 ***