Re: FVWM: xlock...error or ??

From: Robert Nation 885-9815 <rnation_at_mansvr.sanders.lockheed.com>
Date: Thu, 16 Nov 95 12:41:26 EST

>I believe that it may be a little of both. For instance, swirl mode
>(xlockmore 3.2) installs it's own colormap, which works, but then when
>fvwm comes back, The colormap doesn't get restored correctly. So, I
>would assume that passing in -install for blank mode should work this
>way as well, but as you see it doesn't. I'll look into this (adding
>it to TO-DO list).

my guess is that the screen saver users an override-redirect window.
Somewhere along the line, I added code which made fvwm get sloppy about
colormaps when override-redirect windows were present. This was done
for WABI, which is also override-redirect, and sometimes installs its
own colormap. Most likely, fvwm doesn't notice when the override-redirect
window goes away, so it doesn't restore the colormap correctly (or maybe,
the override-redirect window doesn't go away, it just unmaps or something).

As I recall, the ICCCM doesn't say how to handle colormaps for
override-redirect windows, so I couldn't say what the correct behavior is.

Rob

--
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 Nov 16 1995 - 11:43:26 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:57 BST