From: Steven Johnson <sbjohnson@ozemail.com.au>
To: James Ingham <jingham@cygnus.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: Register Window Height Patch
Date: Mon, 03 Apr 2000 16:10:00 -0000 [thread overview]
Message-ID: <38E8976C.A4B1A75E@ozemail.com.au> (raw)
In-Reply-To: <14569.7315.271935.303866@leda.cygnus.com>
Jim,
I agree with you on the vertical height resizing. I did this as
something quick so that
I can have a window higher than 16 which is too small when your CPU
has 165 registers.
Thanks for the info, Following is a revised patch, that icorporates
your comments.
(Hopefully in a better format than the previous one)
Steven Johnson
diff -C2 -r ../gdb_cvs/src/gdb/gdbtk/library/prefs.tcl
src/gdb/gdbtk/library/prefs.tcl
*** ../gdb_cvs/src/gdb/gdbtk/library/prefs.tcl Tue Mar 28 11:59:40 2000
--- src/gdb/gdbtk/library/prefs.tcl Mon Apr 3 22:59:46 2000
***************
*** 311,314 ****
--- 311,315 ----
# Register Window
pref define gdb/reg/highlight_fg blue
+ pref define gdb/reg/rows 16
# Global Prefs Dialogs
diff -C2 -r ../gdb_cvs/src/gdb/gdbtk/library/regwin.itb
src/gdb/gdbtk/library/regwin.itb
*** ../gdb_cvs/src/gdb/gdbtk/library/regwin.itb Wed Mar 29 09:04:13 2000
--- src/gdb/gdbtk/library/regwin.itb Mon Apr 3 22:59:47 2000
***************
*** 348,352 ****
# ------------------------------------------------------------------
body RegWin::dimensions {} {
! set rows 16
# set rows [expr int(floor(sqrt($num_regs)))]
set cols [expr {int(ceil(sqrt($num_regs)))}]
--- 348,352 ----
# ------------------------------------------------------------------
body RegWin::dimensions {} {
! set rows [pref get gdb/reg/rows]
# set rows [expr int(floor(sqrt($num_regs)))]
set cols [expr {int(ceil(sqrt($num_regs)))}]
next prev parent reply other threads:[~2000-04-03 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 15:03 Steven Johnson
2000-04-03 15:32 ` James Ingham
2000-04-03 16:10 ` Steven Johnson [this message]
2000-04-03 16:44 ` James Ingham
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=38E8976C.A4B1A75E@ozemail.com.au \
--to=sbjohnson@ozemail.com.au \
--cc=insight@sourceware.cygnus.com \
--cc=jingham@cygnus.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).