On Thu, 27 Dec 2001, Mikhael Goikhman wrote:
> On 26 Dec 2001 23:21:00 -0800, Tenebrae wrote:
> > This sounds cool if it would work for me. I can't seem for the life of me
> > to get the grey border out of my inactive windows.
> > I have a nice dark purple border with a thin grey border around the
> > outside of my inactive windows. I'd rather that was another shade of
> > purple.
> > Also, the raised buttons etc. in my inactive windows have a grey 3d
> > shading. I'd love to get rid of that and replace it with another shade of
> > purple.
> > I'm not getting the man pages or something.
> > Most .fvwm2rc files seem to use a pixmap for their window borders. I
> > prefer a thin border with a bit of colour to it.
> > I got it to work in FVWM 2.2.4, but am having no luck in 2.4.3.
> > Still trying to stamp out all dull grey in my desktop...
>
> It is hard to understand what "a nice dark purple border with a thin grey
> border" mean without a config and/or screenshot.
You're right. I should have included these to begin with.
Screenshot:
http://www.niceboots.com/~tenebrae/pics/tenebrae_fvwm2.4.3_screenshot.jpg
I added the red arrow and text to emphasize the parts I'm not
liking. Er...please ignore the Gimp plugin errors in that window. :/
My config file is still a bit messy, but I think these are the relevant
parts (in the order that they appear):
ImagePath /usr/share/icons/:/usr/share/icons/mini/:/usr/X11R6/include/X11/bitmaps/:/usr/share/pixmaps/
Style "*" Font -adobe-helvetica-bold-r-*-*-14-*-*-*-*-*-*-*
Style "*" IconFont fixed
# Testing 12/27/2001 - MDM
# I choose ludicrous colours for testing so they will stand out.
Style * BackColor PapayaWhip, ForeColor LightSkyBlue
Style * HilightFore #ffe22d, HilightBack #3C025E
AddToDecor Default
+ BorderStyle Inactive -- Sunk
+ BorderStyle Active -- Raised
+ TitleStyle Inactive TiledPixmap darkpurplebar.xpm
+ TitleStyle ActiveUp TiledPixmap purplebar.xpm
+ ButtonStyle 1 MiniIcon
Style "*" Title, Color Black/#22152B
> If you don't like the CDE-like shadow/hilite color calculations (I also
> don't like them) where the shadow color may be lighter than the background
> color, you should use colorsets and define "sh" and "hi" colors yourself.
> But shadow color of dark purple should not be pure gray like you say, it
> should be something like light purple, so probably your problem is other.
Probably something to do with the Title I set...
> You can't use colorset commands together with the old-style commands,
> i.e. HilightColorset overrides HilightBack and HilightFore.
>
> Also, in my parent message I intentionally did not mention TitleStyle,
> it overrides BackColor and HilightBack (and Colorset and HilightColorset).
Hm.
> If I was screwed with configs, I would start with an empty .fvwm2rc (or
> with only bindings and menus) and add window look commands one by one
> (don't add a command if it does not do you anything good). This way the
> config is minimal and readable. For example start with this .fvwm2rc:
>
> Style * BackColor purple, ForeColor gray # inactive windows
> Style * HilightBack MediumPurple, HilightFore white # active window
>
> Key F11 A CS Restart
> Key F12 A CS Quit
That worked, so obviously I've made a mess of my config file and don't
quite understand what I'm doing. I should start from scratch. This is
what I get for trying to convert dot files between fvwm versions without
fully understanding all the commands.
Need more dot file examples...
Something is overriding the active/inactive window colours.
> If needed, download fvwm-themes and learn its configs, it uses colorsets.
I'm still putting that off.
Thanks.
-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 - 08:54:34 GMT
