On Wed, Aug 01, 2001 at 11:48:04PM -0400, Bob Woodside wrote:
> Bob Woodside wrote:
> >
> > Dominik Vogt wrote:
> > >
> > > ? On the other hand it seems SuSE 7.2 ships with a much improved
> > > xfm version (1.4.2.patchl04). Perhaps the problem has been solved
> > > there.
> >
> > Curious...I grabbed the 1.4.2p4 tarball, and it does indeed work.
> > Their
> > Changelog mentions a fix (in 1.4.2p3) that addresses this: "double
> > clicks in the file window finally work in ol[v]wm/kwm even if the focus
> > policy is "click to focus" (app window still needs to be fixed)". I'll
> > have to see what they did, and discuss it with the current maintainer.
>
> I discussed this with Till Straumann, who made this fix for xfm. He
> said that they'd found that, under kwm and ol(v)wm, extraneous
> EnterNotify/LeaveNotify events were getting sent to the widgets on which
> double clicks failed, which seemed to confuse the XtTranslations stuff
> used to catch a double click. His workaround was to insert an event
> handler that would simply eat these events.
>
> This is exactly what is happening with FVWM now (in ClickToFocus mode),
> and it looks like a bug to me. I know, what the window manager does
> isn't supposed to interfere with the top level's interaction with its
> children, but that appears to be what we're doing, somehow.
>
> To test this, I created a minimal program with a label widget and an
> XtTranslations string to catch a double click. It fails. I added an
> event handler to eat the extra events, just like the one in the latest
> xfm, and it works.
>
> The source is attached. Compile it as it is and run it with MouseFocus,
> and the label text changes when you double click on it; with
> ClickToFocus, it fails. Comment out the line "#undef
> EATENTERLEAVEEVENTS", and the event handler eats the extra events and
> the program works under either focus policy.
>
> I don't have any idea yet where the problem lies or when it may have
> been introduced ("sometime within the past year" covers a lot of
> territory). The only thing I'm pretty sure of now is that it's *not* in
> your changes to the grab code (well, that's the area where one of us -
> probably me - introduced this symptom before).
>
> Any ideas?
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.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
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]
