On Fri, Oct 01, 1999 at 12:16:32AM -0700, raj_at_cisco.com wrote:
> I'm not completely sure this is a bug in fvwm2, but it's not a problem
> with twm. I'm trying to make my way through the fvwm2 code (which
> badly needs more commenting!), but thought I'd see if anyone else has
> seen this as well.
>
> Open an xemacs window. Now execute "make-frame" to open another frame
> on top of your current one. Now iconify the top frame by executing
> the "Iconify" function while your mouse is inside the window. (I
> bound "Iconify" to mouse button 1 along with alt.)
> When the top frame disappears and is iconified, the lower frame should
> automatically get the keyboard focus. It doesn't. The keyboard focus
> is still with the window which is now iconified! Moving the mouse out
> of the window and back in again corrects the problem.
>
> Has anyone else seen this? Is there some configuration which I'm
> missing which corrects it? (I'd hate to spend a lot of time trying to
> fix a "bug" only to find it's my configuration. :-) Does anyone have
> any pointers on where to look for the problem?
I have no idea what your problem is. With the current development
code I can't see it. What is your fvwm version and what focus policy
are you using? Possibly this was a bug in some older fvwm version.
> Incidently, if the window below is some other program it gets keyboard
> focus just fine, so it must have something to do with the way fvwm2
> handles multiple windows which are all part of the same program.
Unlikely. Fvwm doesn't care which application started a window.
Bye
Dominik ^_^
--
Dominik Vogt, Hewlett-Packard GmbH, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/14-4596, fax: 07031/14-3883, dominik_vogt_at_hp.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Oct 01 1999 - 05:21:41 BST