On Mon, 18 Aug 1997, T. Piepho wrote:
#> On Mon, 18 Aug 1997, Christopher Wolf wrote:
#> > I find that the WindowList action, when initiated from the keyboard,
#> > and in the situation where the window is also chosen using the
#> > keyboard, that the window chosen is not focused correctly.
#> >
#> Are you using pointer focus? This is probably a problem I had, where
#> selecting a window from the win list wouldn't give it focus.
I use the default MouseFocus, which is what I assume you mean by
pointer focus.
#> fvwm does in fact give the window focus. It then takes the focus away
#> because the pointer isn't in the window. Make sense? Anyway, I made a patch
#> that warps the pointer to the window so it will keep focus. I use it so I ca
#> switch windows with the keyboard using WindowList (bound to compose). I don'
#> know if this is best solution because pointer warping is generally considered
#> evil, but it works for me.
Well the default WindowList action is to warp to the window after
Focusing and Raising the window, but it does not seem to be happening
correctly. I do see the same thing you see -- that it does get the
focus for a while -- and I was trying to debug to see if the problem
was the menu code trying to put the mouse/focus back (somewhere) when
it was done or maybe something just not executing, but - alas - the
network went down right as I closed in on it.
Anyone have any info?
#> I don't know why you need a dumb terminal to debug fvwm. I don't have one.
#> I just have a menu option to restart to an xterm, which I can then start
#> the fvwm I've compiled from. Any debugging messages fvwm prints then go
#> to the xterm.
When I say debug, I mean line by line with a debugger through the
appropriate regions. And if that region is something like do_menu,
where the focus is moved for a short time to pop up the menu, then I
lose focus on my gdb debugging window when the routine moves the focus
to the menu, pretty much killing the whole deal right there. Can't
type (no focus!), can't refocus (no window manager!). Need a dumb
terminal to allow things to work right.
I've heard one can "nest" window managers somehow to allow debugging
of one of them while the other kicks in to allow you to continue to
move about, but could not find info on it. Anyone have some info on
how it's done by the pro's?
-W
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Aug 19 1997 - 00:29:50 BST