>>>>> "Todd" == Todd Fries <tfries_at_umr.edu> writes:
Todd> The situation:
Todd> I run 'xlock -blank' so as to not annoy my rommate when I
Todd> go to bed. I get a white screen.
Todd> The details:
Todd> (relevent portions of files read by .fvwmrc: )
Todd> ColormapFocus FollowsFocus
Todd> Style "*" SloppyFocus
Todd> which results in I can have my mouse over, netscape, or xdoom,
Todd> and move it away, and the colormap doesn't shift and I don't
Todd> have to keep the mouse in the window...
Todd> However, when I run xlock, to brin the menu up from the
Todd> backgorund, momentarily, the pallette switches from the netscape
Todd> pallete to the 'normal' "fvwm's" colormap, and then back to the
Todd> netscape colormap as I release the xlock menuitem, as it should.
Todd> However, running 'xlock -install' does not allow 'xlock -install
Todd> -mode blank' to show a 'blank, black' screen, instead a
Todd> palette-shifted blazing white!
Todd> Is this the wm or xlock's problem?
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).
It is getting better though, since swirl mode never really worked w/
fvwm (1.xx) in the past, I believe.
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 - 08:51:34 GMT