FVWM Bug Tracking notification
new message incoming/784
Message summary for PR#784
From: [EMAIL PROTECTED]
Subject: Certain thin borders do not get redrawn after expose
Date: Thu, 20 Sep 2001 17:29:38 -0500
0 replies 0 followups
====> ORIGINAL MESSAGE FOLLOWS <====
>From [EMAIL PROTECTED] Thu Sep 20 17:29:39 2001
Received: from karazm.math.uh.edu ([129.7.128.1])
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 15kCKB-00017V-00
for [EMAIL PROTECTED]; Thu, 20 Sep 2001 17:29:39 -0500
Received: from malifon.math.uh.edu (IDENT:[EMAIL PROTECTED] [129.7.128.13])
by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id RAA12339
for <[EMAIL PROTECTED]>; Thu, 20 Sep 2001 17:29:38 -0500 (CDT)
From: [EMAIL PROTECTED]
Received: from localhost ([127.0.0.1] ident=65534)
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 15kCKA-00017R-00
for [EMAIL PROTECTED]; Thu, 20 Sep 2001 17:29:38 -0500
To: [EMAIL PROTECTED]
Subject: Certain thin borders do not get redrawn after expose
Message-Id: <[EMAIL PROTECTED]>
Date: Thu, 20 Sep 2001 17:29:38 -0500
Full_Name: Kekoa Proudfoot
Version: 2.2.4
CVS_Date:
OS: redhat 7.1
X_Server: xfree86
Submission from: (NULL) (171.64.77.61)
The following FVWM config file style causes borders which are not redrawn
after they are exposed:
Style "*" MWMBorder, BorderWidth 1, NoHandles
The easiest way to see this is to place the top window over a window with
these thin borders, then move the top window away. That should make it
pretty obvious, especially if the top window's contents are significantly
different from the border color.
Playing around with this some, I did find a workaround, which is to turn
off MWMBorder using FVWMBorder. Since the borders are so thin they appear
identical using this method.
-Kekoa
--
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]
