From: Keith Seitz <keiths@cygnus.com>
To: Insight Maling List <insight@sources.redhat.com>
Subject: [RFC] New font preferences...
Date: Wed, 18 Jul 2001 15:51:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0107181537370.25148-100000@makita.cygnus.com> (raw)
Hi,
Well, in my continuing quest to make Insight look coherent (and eliminate
Tix), I would like to elicit some feedback about a proposal to introduce
some new font attributes:
gdb/font/highlight_fg
gdb/font/highlight_bg
When highlighting changes (like in RegWin or VariableWins), this
is the foregrond and background colors.
gdb/font/normal_fg
gdb/font/normal_bg
This is the normal font fg/bg. Note that normal_bg should probably
also be the background color of the window. I think this should be
a requirement in all of our windows.
gdb/font/select_fg
gdb/font/select_bg
The selection foregorund/background. Needed to get rid of the
silly "tixOption" stuff all over, too.
gdb/font/header_fg
gdb/font/header_bg
For windows with headers (like tables in MemWin, RegWin, and
VariableWins), this defines the fg/bg.
Maybe there are more, but these are what I used when I rewrote RegWin.
Comments on this?
Next: default values:
gdb/font/highlight_fg blue
gdb/font/highlight_bg gray92
gdb/font/normal_fg black
gdb/font/normal_bg gray92
gdb/font/select_fg black
gdb/font/select_bg lightgray
gdb/font/header_fg gray92
gdb/font/header_bg darkgray
So basically, I'm saying that the background of ALL windows should be
"gray92". Right now some windows use "white" and some use "gray92". I like
"gray92" better than white, since the white tends to bleed on CRTs.
(Of course, this means adding more preferences for this, but...)
Like it/hate it?
Keith
reply other threads:[~2001-07-18 15:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.33.0107181537370.25148-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).