Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!haven!decuac!shlump.nac.dec.com!rust.zso.dec.com!bacchus.pa.dec.com!decwrl!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: Can't set borderColor
Message-ID: <1990Aug31.232455.3237@wrl.dec.com>
Date: 31 Aug 90 23:24:55 GMT
References: <1990Aug31.171825.13477@laguna.ccsf.caltech.edu>
Sender: news@wrl.dec.com (News)
Reply-To: klee@wsl.dec.com
Organization: DEC Western Software Laboratory
Lines: 24


In article <1990Aug31.171825.13477@laguna.ccsf.caltech.edu>,
johns@macondo.ccsf.caltech.edu (John Salmon) writes:
|> Nothing I do seems to affect the
|> color of the borders that I see on the screen.

Top level window borders are generally overwritten by the window
manager, thus you must set the colors through the window manager.

|> Additionally, could someone provide a simple explanation of the
|> purpose of the two types of separators, '.' and '*' in .Xdefaults
|> files, as well as some rule of thumb about when to say, e.g.:
|> Emacs*BorderColor vis a vis emacs*borderColor

For multi-level resources . matches exactly 1 level, while * matches
any number of levels.  Emacs vs. emacs and BorderColor vs. borderColor
is specified by the client, but generally the capitalized names are the
class names while the non-capitalized names are the instance names.  Yes,
resources are heirarchical and object oriented.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee