public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Martin M. Hunt" <hunt@redhat.com>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: New locals and watch windows
Date: Wed, 06 Nov 2002 13:55:00 -0000	[thread overview]
Message-ID: <1036619783.2085.40.camel@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]

I have just checked in a complete rewrite of the local and watch
windows.  The new window use a new VarTree widget instead of the old Tix
tree widget. The VarTree widget is a pure itcl tree widget that is
designed specifically to display varobjs.

I will not be including any diffs because everything is different.

2002-11-06  Martin M. Hunt  <hunt@redhat.com>

	* library/watch.tcl: Completely rewritten to use VarTree.
	* library/locals.tcl: Completely rewritten to use VarTree.
	* library/variables.tcl: Deleted.
	* library/vartree.ith: New file.
	* library/vartree.itb: New file. Implements a variable
	tree.
	* library/tclIndex: Rebuilt.

I'm attaching some screenshots.  In the Watch window you can see that
"args" and "endp" are not currently valid so they are automatically
grayed out.  There is no menubar; instead a right mousebutton over a
variable pops up a menu.  Right mousebutton over empty space pops up a
smaller menu with just "Sort, Help, and Close".  The reason for this is
simply to maximize the useful space.

You can edit an entry by double-clicking on the value or using the
pop-up menu.

In the screenshot of the locals window, you can see the right
mousebutton popup menu.  If you click on a variable you get the same
menu as the one in the picture of the watch window.  The only difference
between the watch and locals window appearance is that the watch window
has an entry field at the bottom.  I am thinking of removing it and
adding it to the popup menu instead.  Any opinions?

Martin


[-- Attachment #2: Type: image/png, Size: 14695 bytes --]

[-- Attachment #3: locals.png --]
[-- Type: image/png, Size: 12694 bytes --]

                 reply	other threads:[~2002-11-06 21:55 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=1036619783.2085.40.camel@localhost.localdomain \
    --to=hunt@redhat.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).