public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Mike Clarkson <support@internetdiscovery.com>
To: "Left Spin" <leftspin@hotmail.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Debugging SourceNavigator
Date: Fri, 14 Dec 2001 09:25:00 -0000	[thread overview]
Message-ID: <3.0.6.32.20011214092227.008fb2e0@popd.ix.netcom.com> (raw)
Message-ID: <20011214092500.lKOTewx4aYKWt1NpZ1ZgHnCdD71uTc8g8bAm9W0K99k@z> (raw)
In-Reply-To: <F1359isZ24dsPkskqed00001d79@hotmail.com>

At 01:18 AM 12/13/01 +0000, you wrote:
>I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr 
>tcl/tk], but now I'm at a loss on how you debug the running application. I'm 
>having trouble following the state variables of the megawidgets, and I'd 
>really like to be able to set break points in the tcl/tk code and examine 
>objects.

There's a very good debugger/inspector for Tcl/Tk/Tix called TixInspect,
which has a basic but fairly useful debugger built into it. The inspector
lets you see
everything, and modify things on the fly - it's very powerful. Look at

	http://tix.sourceforge.net/Tixapps

To use SN with TixInspect under Unix, you'll have to comply with Tk's
semi-rigorous demands for Xauth authentication and no xhosts, or recompile the
tk dynamic library with this turned off. In the Makefile for tk, look for

# To turn off the security checks that disallow incoming sends when
# the X server appears to be insecure, reverse the comments on the
# following lines:
SECURITY_FLAGS = 
#SECURITY_FLAGS = -DTK_NO_SECURITY

Then in the SN code, if it's not already there, add the following line;

	tk appname "SN#[winfo id .]"

To use SN with TixInspect under Windows, you'll have make sure the 
Tcl tcldde83.dll is available either in the directory with with the tcl83.dll
or in lib/tcl8.3/dde1.0 (replace 83 with whatever verion of Tcl you're using).

Then in the SN code, if it's not already there, add the following lines;

	package require dde
	dde servername "SN#[winfo id .]"

>Any help would be appreciated. My goal is to provide fixes to the source, 
>and add an optional new editor keybindings configuration file (wordstar to 
>start with).

TixInspect is the revised updated version of the time-honoured Tkinspect,
and is built for Tix applications such as SN. OTOH, if I had of known you
were going to use it for adding Wordstar bindings, I would never have
released it:-)

Mike.

  reply	other threads:[~2001-12-14  9:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 14:19 Left Spin
2001-11-27 17:10 ` Mike Clarkson [this message]
2001-12-14  9:25   ` Mike Clarkson
2001-12-12 17:18 ` Left Spin
2001-11-24 14:01 Left Spin
2001-11-24 14:40 ` Mike Fahlbusch
2001-11-26  0:23   ` Syd Polk
2001-11-29 23:46     ` Mike Clarkson
2001-12-14 11:14       ` Mike Clarkson
2001-12-12 22:52     ` Syd Polk
2001-12-12 18:03   ` Mike Fahlbusch
2001-12-12 17:19 ` Left Spin
2001-11-25 18:28 Left Spin
2001-12-12 18:06 ` Left Spin

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=3.0.6.32.20011214092227.008fb2e0@popd.ix.netcom.com \
    --to=support@internetdiscovery.com \
    --cc=leftspin@hotmail.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).