From: Bruce Dawson <bruced@valvesoftware.com>
To: "insight@sourceware.org" <insight@sourceware.org>
Subject: Too many windows
Date: Tue, 26 Feb 2013 01:10:00 -0000 [thread overview]
Message-ID: <2AC155A009400B4C8B05D518E4819AEF0719DBB1@exchange10.valvesoftware.com> (raw)
Normally when I'm debugging I like having a source window, disassembly window, registers window, call stack window, command/output window, and a call stack window -- I feel like that's a good starting point. The compelling advantage of Insight is that it lets me do this.
However...
In Insight each of these windows is independent. That means that if I bring the inferior's window to the front and then want to bring Insight back to the front I have to bring five or six windows forward. Is there any way to tie the Windows together so that they only show up once in the alt+tab listing and so that they all move to the front together? The fact that all of the Windows have identical generic icons makes it more frustrating.
Docking the windows into the 'main' window would be one way of dealing with this, but I'll take whatever works.
A related issue is that the keyboard accelerators are local to particular Windows -- 'S' and 'N' only work when the main window is active. I guess I could redundantly map the accelerators to the other windows, with a bit of work.
Any thoughts on how practical it is to tie the Windows together somehow?
reply other threads:[~2013-02-26 1:10 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=2AC155A009400B4C8B05D518E4819AEF0719DBB1@exchange10.valvesoftware.com \
--to=bruced@valvesoftware.com \
--cc=insight@sourceware.org \
/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).