public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Insight Maling List <insight@sources.redhat.com>
Subject: [PATCH] Set bpwin initial size
Date: Thu, 14 Mar 2002 09:11:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0203140908220.11890-100000@makita.cygnus.com> (raw)

Hi,

The breakpoint window is using iwidgets::scrolledframe, which uses a
canvas for layout. As with all canvases, initial size of the canvas is a
default 100x100, and it consequently doesn't look very nice.

This silly patch adds an initial default size of 350x165 for the BpWin.
This geometry can be overriden by ManagedWin and user preferences, and it
should be pretty harmless. If it isn't, we can fix it if someone says
something.

Keith

ChangeLog
2002-03-14  Keith Seitz  <keiths@redhat.com>

	* library/bpwin.itb (constructor): Set some sane initial
	size.

Patch
Index: gdb/gdbtk/library/bpwin.itb
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/bpwin.itb,v
retrieving revision 1.12
diff -p -c -2 -p -r1.12 bpwin.itb
*** gdb/gdbtk/library/bpwin.itb	2002/03/07 06:06:18	1.12
--- gdb/gdbtk/library/bpwin.itb	2002/03/14 17:03:16
*************** body BpWin::constructor {args} {
*** 26,29 ****
--- 26,35 ----
    build_win
    eval itk_initialize $args
+
+   # The scrolledframe uses a canvas, which doesn't properly
+   # calculate an initial size, so we must set a default
+   # window size here. ManagedWin could override this still
+   # if there is a user preference for the geometry.
+   wm geometry $_top 350x165
    debug "done building"
  }

                 reply	other threads:[~2002-03-14 17:11 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=Pine.GSO.4.33.0203140908220.11890-100000@makita.cygnus.com \
    --to=keiths@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).