From: khamis2@t-online.de (Khamis Abuelkomboz)
To: Bruce Edson <bruce@steptech.com>
Cc: "Sourcenav (E-mail)" <sourcenav@sources.redhat.com>
Subject: Re: SN5.0e error
Date: Wed, 10 Apr 2002 12:28:00 -0000 [thread overview]
Message-ID: <3CB4926F.1060408@t-online.de> (raw)
In-Reply-To: <26F9F6EAB586D411850700B0D049E6E4014D2F75@shasta.pdx.steptech.com>
Yes, there is a bug here, for a quick fix, you need to replace the line
<SN50E>/share/sourcenav/gui/xrefpante.tcl:2279: for {set i 0}
{${i} <= ${tabsize}} {incr i} {
with
<SN50E>/share/sourcenav/gui/xrefpante.tcl:2279: for {set i 0}
{${i} < ${tabsize}} {incr i} {
I will post a new update for SN50E fixing a bug in Makefiles and defines
the parsers
with more extensions. Also keeping current directory on unix platforms
doesn't
work.
khamis
Bruce Edson wrote:
>Hi Khamis,
>
>We've been playing around with your new version of SN (5.0e). It looks
>pretty good and worth moving to for us. However, there is a bug, that
>didn't exist in the original SN5.0, with the 'Details by' popup available on
>an XRef pane. The 'Details to' may be affected as well. The program issues
>the following error message:
>
>invalid command name
>".multiwindow-2.paned.main.nbook.nbframe.xref.paned.xref.xref.can.w-by-1.sel
>.size.btn5"
> while executing
>"${ifr}.size.btn${i} configure -background ${bg}"
> (object "::.multiwindow-2.paned.main.nbook.nbframe.xref.paned.xref.xref"
>method "::XRef&::xbrowse" body line 91)
> invoked from within
>"::.multiwindow-2.paned.main.nbook.nbframe.xref.paned.xref.xref xbrowse by"
> (menu invoke)
>
>Any clues on a fix for this? This is a 'must have' for us.
>
>Thanks
>
>Bruce
>
>
--
--
Dipl.-Informatiker
Khamis Abuelkomboz
Rosenweg 124
58239 Schwerte
+49 2304 898560 (Telefon)
+49 2304 898561 (Fax)
http://khamis.oimanager.de
prev parent reply other threads:[~2002-04-10 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 11:39 Bruce Edson
2002-04-10 12:28 ` Khamis Abuelkomboz [this message]
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=3CB4926F.1060408@t-online.de \
--to=khamis2@t-online.de \
--cc=bruce@steptech.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).