From: khamis2@t-online.de (Khamis Abuelkomboz)
To: "Parker, Ron" <rdparker@butlermfg.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Bold Text in Hierarchy Browser
Date: Tue, 11 Dec 2001 20:57:00 -0000 [thread overview]
Message-ID: <3C2BB299.1050005@t-online.de> (raw)
In-Reply-To: <E94FF01DFF6CD31186F4080009DC361503E88508@nttwr2.tower.bldgs.butlermfg.org>
Parker, Ron wrote:
>I have been using Source-Navigator and greatly appreciate the work that has
>been put into it. Thanks one and all.
>
>Why are some classes in the hierarchy browser shown in bold and others are
>not?
>
>If you know, please respond directly to me and to the list since I am not a
>subscriber, but I did try to find it in the archives.
>
the bold classes contain virtual members!
WARNING: multiple messages have this Message-ID
From: khamis2@t-online.de (Khamis Abuelkomboz)
To: "Parker, Ron" <rdparker@butlermfg.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Bold Text in Hierarchy Browser
Date: Thu, 27 Dec 2001 15:44:00 -0000 [thread overview]
Message-ID: <3C2BB299.1050005@t-online.de> (raw)
Message-ID: <20011227154400.AQ1ulCjdBA9c10APqLlxiTLkWLCK-qyTr9KVgdQHnKc@z> (raw)
In-Reply-To: <E94FF01DFF6CD31186F4080009DC361503E88508@nttwr2.tower.bldgs.butlermfg.org>
Parker, Ron wrote:
>I have been using Source-Navigator and greatly appreciate the work that has
>been put into it. Thanks one and all.
>
>Why are some classes in the hierarchy browser shown in bold and others are
>not?
>
>If you know, please respond directly to me and to the list since I am not a
>subscriber, but I did try to find it in the archives.
>
the bold classes contain virtual members!
next prev parent reply other threads:[~2001-12-27 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 20:30 Parker, Ron
2001-12-11 20:57 ` Khamis Abuelkomboz [this message]
2001-12-27 15:44 ` Khamis Abuelkomboz
2001-12-27 9:28 ` Parker, Ron
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=3C2BB299.1050005@t-online.de \
--to=khamis2@t-online.de \
--cc=rdparker@butlermfg.com \
--cc=sourcenav@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).