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 166779 - gok mouse latching regressed
gok mouse latching regressed
Status: RESOLVED FIXED
Product: gok
Classification: Deprecated
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: bill.haneman
bill.haneman
AP1
Depends on:
Blocks:
 
 
Reported: 2005-02-09 12:41 UTC by bill.haneman
Modified: 2005-02-09 14:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6

Attachments
patch to restore this functionality (1.54 KB, patch)
2005-02-09 12:43 UTC, bill.haneman 		accepted-commit_now Details | Review

Description bill.haneman 2005-02-09 12:41:26 UTC 
run gok using an extended input device (e.g. XInput).
Use the 'Mouse' keyboard's 'Pointer' command. 

Move the "gok pointer" outside the GOK window.

expected behavior: core pointer warps to the gok pointer and follows the
extended input device until it re-enters the GOK window.

observed behavior: core pointer warps to gok pointer but almost immediately
unlatches.

This seems to have been caused by GDK "enter notify" events from
"inferior"windows, i.e. the pointer moves from a child window into the
containing GOK GtkWindow.  This may be a regression caused by subtle behavioral
changes in gtk+ as compared with the old gtk+ 2.2 series.

Fix is to ignore enter-notify events from inferiors (and so-called "nonlinear
virtual" enter-notify events) in this case.

Fix on the way.
Comment 1 bill.haneman 2005-02-09 12:43:13 UTC 
Created attachment 37235 [details] [review]
patch to restore this functionality
Comment 2 David Bolter 2005-02-09 14:11:15 UTC 
Comment on attachment 37235 [details] [review]
patch to restore this functionality

Nice catch.  I guess this should be added to our test battery.