On Fri, Aug 17, 2001 at 03:18:18PM -0400, Bob Woodside wrote:
Bob Woodside wrote:
Well, this one has led me a merry chase...and I'm still chasing.
The problem seems to be mostly confined to focus.c:
focus_grab_buttons,
which doesn't quite work as intended. I've
Dominik Vogt wrote:
However, with your patch, fvwm passes through the for (...) loop
much more often then necessary. Could you try to write some
condition like the former
if (grab_buttons != tmp_win-grabbed_buttons)
to prevent fvwm from entering the loop unnecessarily?
Yeah,
On Sun, Aug 19, 2001 at 01:36:24PM -0400, Bob Woodside wrote:
Dominik Vogt wrote:
However, with your patch, fvwm passes through the for (...) loop
much more often then necessary. Could you try to write some
condition like the former
if (grab_buttons != tmp_win-grabbed_buttons)
Bob Woodside wrote:
Well, this one has led me a merry chase...and I'm still chasing.
The problem seems to be mostly confined to focus.c:
focus_grab_buttons,
which doesn't quite work as intended. I've hacked it up to the point
where it does what I think was intended. It
Well, this one has led me a merry chase...and I'm still chasing.
To recap the problem: it boils down to the need to suppress Xlib's
automatic grab when a mouse button is pressed, and the unwanted
LeaveNotify/EnterNotify
events generated by that grab; and it's the Leave/Enter
Bob Woodside wrote:
Dominik Vogt wrote:
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.
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
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
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
Dominik Vogt wrote:
I see no problem at all. Are you sure you are using
Style * ClickToFocusPassesClick
Yup.
? 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
On Fri, Jul 27, 2001 at 01:54:44PM -0400, Bob Woodside wrote:
Hi, all --
After way too long an absence, I finally got around to installing
2.4.0, and discovered that the old no double-clicks getting passed to
xfm and moxfm problem that I fixed back in December of 1999 has
resurfaced,
Hi, all --
After way too long an absence, I finally got around to installing
2.4.0, and discovered that the old no double-clicks getting passed to
xfm and moxfm problem that I fixed back in December of 1999 has
resurfaced, at least partly. This time it only appears to affect
ClickToFocus
12 matches
Mail list logo
