Dominik Vogt wrote:
>
>
> Well, that does not sound strange at all. I guess the widget
> window has not selected Enter/Leave events, but it has selected
> ButtonPress events. Thus, clicking into the widget window
> should generate Enter/LeaveNotify events on the widget window.
> If the application does not want these events it should not select
> them, right?
>
> Anyway, if you send me your sample program I'll have a look at the
> problem.
Erm...it was attached to the last email. However, ignore it. I'll send
you a revised version, if you like, that reveals more information.
Here's what it shows.
The Leave/Enter events are semi-spurious. They occur (in that order)
between every Btn1Down and Btn1Up, and they have mode = NotifyGrab and
mode = NotifyUngrab, respectively. This happens when the pointer gets
grabbed away from the window it's currently in. It looks like we're
grabbing way too often - or possibly even doing the whole focus thing
too often - on every single click. This should happen only on the first
click needed to transfer focus to the window, not on subsequent clicks
when the window already has the focus. It confuses the Xt lib routines
that handle double click detection.
Now that I understand what's happening from the app's perspective,
maybe I can figure out where we went astray...if you don't beat me to
it!
Cheers,
Bob
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
