Re: Changing background colors

[lrcgtk red4est com]

On Fri, May 14, 2004 at 05:04:24PM +0200, Diego Zuccato wrote:
> John Cupitt wrote:
> 
> > You should be able to change the whole application with just your gtkrc. Try this in your ~/.gtkrc-2.0 file and (almost) everything should go a very ugly pink:
> > 
> > style "pink"
> > {
> >   bg[NORMAL]      = { 1.000, 0.80, 0.80 }
> >   fg[NORMAL]      = { 1.000, 0.40, 0.60 }
> >   bg[PRELIGHT]    = { 1.000, 0.80, 1.00 }
> >   fg[PRELIGHT]    = { 1.000, 0.40, 0.60 }
> >   bg[ACTIVE]      = { 1.000, 0.80, 0.80 }
> >   fg[ACTIVE]      = { 1.000, 0.40, 0.60 }
> >   bg[SELECTED]    = { 1.000, 0.60, 0.80 }
> >   fg[SELECTED]    = { 1.000, 0.00, 0.00 }
> >   base[SELECTED]  = { 1.000, 0.60, 0.80 }
> >   text[SELECTED]  = { 1.000, 0.00, 0.00 }
> >   base[ACTIVE]    = { 1.000, 0.80, 0.80 }
> >   text[ACTIVE]    = { 1.000, 0.00, 0.00 }
> > }
> > 
> > class "GtkWidget" style "pink"
> Just tried it: I can't change "background" (the white area) of entries,
> combo boxes, treeviews, etc...
> 
> Is there a way to change them?


Which window manager are you running?

I'm running fedora on my laptop and switched between gnome and kde.
I've found that gnome seems to nearly ignore the gtkrc files. You need
to figure out which theme you're using, find where it's kept
(sometimes /usr/share/themes, sometimes ~/.themes) find
gtkrc-2.0/gtkrc under that theme and futz with that, and sometimes
it'll work. Unless you compile under gtk 1 instead of 2.  

In kde, sometimes it seems as if it sometimes uses gtkrc-2.0/gtkrc and
sometimes .gtkrc-2.0. I just symlinked those two files together which
seems to work.

Then there are theme engines, if your gtkrc file has a line under the
default style:
        engine "mist"
        {
        }

that will also affect everything.

Unfortunately, other than putting errors in each gtkrc file that will
get printed out when you try to run your program, I don't know of any
way of finding out what gtkrc file is actually being read. If you do
put an error in, do it at the end, because the system seems to puke on
errors and not read anything in the file after the first error.