From: Ruppert <dieter_ruppert@siemens.com>
To: insight@sourceware.org, valegroup@att.net
Subject: Re: Source mode, function selector and file selector : display pb
Date: Mon, 09 Jan 2006 08:43:00 -0000 [thread overview]
Message-ID: <200601090843.k098hON02168@haiti.swb.siemens.de> (raw)
Hi,
>
>wilfried.fauvel@laposte.net wrote:
>> I have a little problem with Insight (cygwin win32), when I start it, I
>> have to resize the window to view the Source mode, function selector and
>> file selector (under the icons bar). Is there any tips to fix that ?
>
>That's been a problem since the version of about 18 February 2003. The only
>workaround I know of is to slightly adjust the window size. Then the missing
>strip will pop into view.
this is in the bug database as PR 253. I added a workaround description
to this PR some time ago, which unfortunately was a bit garbled. I reproduce
the relevant lines below.
HTH.
Regards
Dieter R.
There is a simple workaround for those who am annoyed by this: inserting
a (invisible) frame with the required height into the row of comboboxes
avoids this. Here is a patch for srcwin.itb (relative to 6.1) which does
this:
*** srcwin.itb.orig Thu Jul 14 09:35:17 2005
--- srcwin.itb Thu Jul 14 09:40:33 2005
***************
*** 106,113 ****
$_statbar.mode list insert end MIXED
$_statbar.mode list insert end SRC+ASM
pack $_statbar.mode -side right -padx 10 -pady 4
! pack $_statbar.name $_statbar.func -side left -pady 4 -padx 10
# if user likes control on top...
if {[pref get gdb/src/top_control]} {
--- 106,119 ----
$_statbar.mode list insert end MIXED
$_statbar.mode list insert end SRC+ASM
+ # Workaround: the three comboboxes above sometimes display with height
+ # of one pixel. Insert a (invisible) frame with the required height
+ # fixes this...
+
+ frame $_statbar.strut -height 24 -width 10
+
pack $_statbar.mode -side right -padx 10 -pady 4
! pack $_statbar.name $_statbar.func $_statbar.strut -side left -pady
4 -padx 10
# if user likes control on top...
if {[pref get gdb/src/top_control]} {
next reply other threads:[~2006-01-09 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 8:43 Ruppert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-12 8:05 Wilfried Fauvel
2006-01-12 12:35 ` Dave Korn
2006-01-12 16:56 ` Keith Seitz
2006-01-12 21:21 ` Vale Group
2006-01-11 9:17 Wilfried Fauvel
2006-01-11 10:29 ` Dave Korn
2006-01-12 0:29 ` Vale Group
2006-01-05 8:47 wilfried.fauvel
2006-01-05 18:55 ` Vale Group
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=200601090843.k098hON02168@haiti.swb.siemens.de \
--to=dieter_ruppert@siemens.com \
--cc=insight@sourceware.org \
--cc=valegroup@att.net \
/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).