> I experienced the puzzling behaviour that the outlines of windows were
> not drawn during resize or move operations on both 16 and 24 bpp
> displays. Looking through the mailing list archives I found that the
> reason is that the default XORValue for those "rubberbands" was
> changed from 255 to 1, giving better results on 8bpp (correct me if
> I'm wrong)
>
> I think this is not a good idea:
>
> The old value was fine (maybe not perfect) for _all_ kinds of
> depths. At least it worked. If one of our users found it
> insufficiently (nobody ever did) she could have easily set the value
> herself. At our site we have the policy to give users a set of
> dotfiles with the promise, that they can get their work done if they
> leave them as they are. These files are minimal, without bells and
> whistles. If users fiddle with them, they're on their own.
> With our "minimal" .fvwmrc they can run the WM, if they want to
> explore its features they have to RTFM.
Having experienced a similar problem in Wine we've settled on
the
(WhitePixelOfScreen(screen) ^ BlackPixelOfScreen(screen))
for GXxor invert. It works as expected in TrueColor and reasonably
good in PseudoColor. I'd suggest to use this as the default XORValue
with .fvwmrc entry overriding it if necessary.
Alex
--
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 Thu Feb 27 1997 - 00:08:50 GMT