On Thu, 27 Dec 2001, Mikhael Goikhman wrote:
> > Style "*" Title, Color Black/#22152B
>
> Don't use Style Color, it was obsoleted years ago and may be removed.
Ah, okay. I guess I didn't understand earlier that this fell under that
category.
Thank you for pointing this out.
As it happens, removing this line entirely and incorporating it into the
Style backcolor/forecolor stuff worked better.
> The problem is, as I said, in CDE-like shadow/hilite color calculations.
> In 2.2.x, GTK-like calculations were used, so for the black background
> shadow color was black (some people think this is good). In 2.4.x, the
> shadow color for the black (or almost black) background is gray.
Ah HA!
Not entirely, it would seem.
(and I'm one of the people who thinks black shadow is good)
> Currently you can't do anything except for using colorsets to replace gray
> with whatever you want, like on the first line here (your colors used):
>
> *FvwmTheme: Colorset 1 bg #22152B, fg black, sh #110A15, hi #442a52
> *FvwmTheme: Colorset 2 bg #3C025E, fg #ffe22d
>
> Style * Colorset 1 # inactive windows
> Style * HilightColorset 2 # active window
>
> DestroyFunc StartFunction
> AddToFunc StartFunction
> + I ModuleSynchronous FvwmTheme
Or...
I could just pick a colour that appears in rgb.txt instead of specifying a
hex colour myself.
Who would have thought it could be something so simple?
I don't have as wide a range of colours to choose from, alas, but I
managed to find a couple shades of purple that suited my purposes, for
now.
My .fvwm2rc file now has:
Style * BackColor purple4, ForeColor Black
Style * HilightFore #ffe22d, HilightBack BlueViolet
(well, and a bunch of other relatively unrelated stuff)
...and I have deleted the line:
Style "*" Title, Color Black/#22152B
Observatory summary:
It would appear that part of my problem was that the default shadow colour
for any custom colour not appearing in rgb.txt is GREY. Please correct me
if I'm wrong.
The other part of my problem was attempting to incorporate old code.
Thank you for helping me narrow this down.
Side note: the function key bindings you had me use in the test .fvwm2rc
didn't work - I have no F11 or F12 on my keyboard and simply changing the
entries to F9 and F10 didn't work. :/ Luckily, FVWM2 appears to have
some sort of built-in menu that it will produce (even in the event of a
fairly empty dot file) which contains a restart and quit option. Cool.
-Tenebrae.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Dec 27 2001 - 21:23:57 GMT