FVWM Bug Tracking notification
new message incoming/941
Message summary for PR#941
From: [EMAIL PROTECTED]
Subject: Icon & window stacking order glitch
Date: Sun, 20 Oct 2002 16:59:10 -0500
0 replies 0 followups
====> ORIGINAL MESSAGE FOLLOWS <====
>From [EMAIL PROTECTED] Sun Oct 20 16:59:11 2002
Received: from util2.math.uh.edu ([129.7.128.23])
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 183O6J-0000Qo-00
for [EMAIL PROTECTED]; Sun, 20 Oct 2002 16:59:11 -0500
Received: from malifon.math.uh.edu ([129.7.128.13] ident=mail)
by util2.math.uh.edu with esmtp (Exim 4.10)
id 183O6J-000524-00
for [EMAIL PROTECTED]; Sun, 20 Oct 2002 16:59:11 -0500
Received: from localhost ([127.0.0.1] ident=65534)
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 183O6I-0000Qk-00
for [EMAIL PROTECTED]; Sun, 20 Oct 2002 16:59:10 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Icon & window stacking order glitch
Message-Id: <[EMAIL PROTECTED]>
Date: Sun, 20 Oct 2002 16:59:10 -0500
Full_Name: Chris Siebenmann
Version: 2.4.12
CVS_Date:
OS: Red Hat Linux 7.3
X_Server: XFree86 4.2.1
Submission from: (NULL) (128.100.102.51)
If I iconify a window (in a style where the icon winds up on the root
window, not swallowed into an FvwmIconManager or the like), the icon is
more or less stuck below all non-icon windows regardless of attempts to
manipulate the stacking order. Everything appears to be on the default
layer (layer 4 in my case), according to FvwmIdentify.
If I perform operations that cause fvwm to refresh the icon, such
as flipping to another virtual screen and then back or moving a
window (with OpaqueMove) such that the icon is partly exposed, the
icon will temporarily pop into visibility in its proper stacking
order. If I raise and then relower an obscuring window, poof the
icon disappears again.
This bug is not entirely consistent; there are some icons that it
doesn't happen to. I can't see a discernable pattern in what they
are, unfortunately.
I do not use an IconBox ('Style * IconBox none').
I can't think of any other relevant styles or elements of my
FVWM configuration. (If I am wrong about this, please let me know
and I will be happy to fill in any necessary details.)
I was previously running FVWM 2.4.3, which did not behave like this.
I am willing to test patches. (Eager, in fact, as I'm finding this
glitch to be quite annoying; I may have to revert to fvwm 2.4.3
temporarily.)
--
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]
