From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6367 invoked by alias); 26 Feb 2013 01:10:11 -0000 Received: (qmail 6355 invoked by uid 22791); 26 Feb 2013 01:10:10 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx3.valvesoftware.com (HELO mx3.valvesoftware.com) (208.64.203.145) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 26 Feb 2013 01:10:05 +0000 Received: from mx3.valvesoftware.com (127.0.0.1) id h5ei7s0171s8 for ; Mon, 25 Feb 2013 09:50:54 -0800 (envelope-from ) Received: from mx3.valvesoftware.com ([172.16.1.53]) by mx3.valvesoftware.com (SonicWALL 7.3.6.7163) with ESMTP; Mon, 25 Feb 2013 09:50:54 -0800 Received: from FEDEX1.valvesoftware.com (172.16.1.101) by exchange10.valvesoftware.com (172.16.1.53) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 25 Feb 2013 17:10:04 -0800 Received: from EXCHANGE10.valvesoftware.com ([fe80::995a:b010:5730:9af]) by fedex1.valvesoftware.com ([::1]) with mapi id 14.02.0318.004; Mon, 25 Feb 2013 17:10:04 -0800 From: Bruce Dawson To: "insight@sourceware.org" Subject: Too many windows Date: Tue, 26 Feb 2013 01:10:00 -0000 Message-ID: <2AC155A009400B4C8B05D518E4819AEF0719DBB1@exchange10.valvesoftware.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EXCLAIMER-MD-CONFIG: 86b76815-e903-4403-b95d-5abb05264373 X-Mlf-Version: 7.3.6.7163 X-Mlf-UniqueId: o201302251750530017224 X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2013-q1/txt/msg00033.txt.bz2 Normally when I'm debugging I like having a source window, disassembly wind= ow, registers window, call stack window, command/output window, and a call = stack window -- I feel like that's a good starting point. The compelling ad= vantage 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 list= ing and so that they all move to the front together? The fact that all of t= he 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.=20 A related issue is that the keyboard accelerators are local to particular W= indows -- 'S' and 'N' only work when the main window is active. I guess I c= ould redundantly map the accelerators to the other windows, with a bit of w= ork. Any thoughts on how practical it is to tie the Windows together somehow?