>>>>> "Rob" == Robert Nation 885-9815 <rnation_at_mansvr.sanders.lockheed.com> writes:
>> 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).
Rob> my guess is that the screen saver users an override-redirect
Rob> window.
Just checked and yes, that's what's happening here. Makes sense,
since they don't want it to have any borders or titles applied to the
window that obscures the entire display.
Rob> Somewhere along the line, I added code which made fvwm get sloppy
Rob> about colormaps when override-redirect windows were present. This
Rob> was done for WABI, which is also override-redirect, and sometimes
Rob> installs its own colormap.
I remember all that. I really hate WABI...
Rob> Most likely, fvwm doesn't notice when the override-redirect
Rob> window goes away, so it doesn't restore the colormap correctly
Rob> (or maybe, the override-redirect window doesn't go away, it just
Rob> unmaps or something).
That seems to be the case.
Rob> As I recall, the ICCCM doesn't say how to handle colormaps for
Rob> override-redirect windows, so I couldn't say what the correct
Rob> behavior is.
I just looked real quick at the ICCCM 2.0 and didn't see any
references to override-redirect at all. I'll take a closer look
later.
Perhaps a global option that means "I'll be using WABI" might be in
order, to account for this, and only do the "sloppyness" if it's set.
Chuck
--
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 - 13:38:43 GMT