[63] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: [bug] motion tracking bug?
daemon@ATHENA.MIT.EDU (Kazuhiro Sasayama)
Wed May 7 01:58:16 1997
To: Owen Taylor <owt1@cornell.edu>
Cc: Kazuhiro Sasayama <kaz@hypercore.co.jp>,
"Adam D. Moss" <adam@uunet.pipex.com>,
gimp-developer@scam.xcf.berkeley.edu, gtk-list@redhat.com
From: Kazuhiro Sasayama <kaz@hypercore.co.jp>
Date: 07 May 1997 14:43:17 +0900
In-Reply-To: Owen Taylor's message of Tue, 06 May 1997 09:48:54 -0400
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
>>>>> "OT" == Owen Taylor <owt1@cornell.edu> writes:
OT> What need to be done is to find out what is clogging up
OT> the event queue - it shouldn't be motion events, since
OT> they are suppressed by GDK_POINTER_MOTION_HINT. Running
OT> the GIMP with --show-events might help.
It showed many motion *hint* events while painting. It seems a call
to XQueryPointer generates another motion event, according to the
description in "Xlib - C Language X Interface."
o PointerMotionHintMask
If PointerMotionHintMask is selected in combination
with one or more of the above masks, the X server is
free to send only one MotionNotify event (with the
is_hint member of the XPointerMovedEvent structure set
to NotifyHint) to the client for the event window,
until either the key or button state changes, the
pointer leaves the event window, or the client calls
XQueryPointer or XGetMotionEvents. The server still
may send MotionNotify events without is_hint set to
NotifyHint.
BTW, is it necessary to ignore pointer positions reported by motion
hint events as gdisplay_canvas_events does?
--
Kaz Sasayama, the designer of Hyperplay.
PGP key fingerprint = 53 71 54 56 FB 3D 76 0B 92 5D 32 40 C5 34 38 00
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
