One more thing. You may want to save off your preferred configuration
to easily restore it back to your favorite settings, since you’re bound
to need to reset it at some point. Just perform step 4 of “Before Using
a Theme” in themes.doc.
Thank you all for your feedback, both positive and negative.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Graham, Simon
Sent: Monday, February 21, 2005 12:53 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Disable the docking windows
OK Jason, you shamed me into spending 20mins setting this up
Well, as you say, using multiple docks pretty much does what I want
although I see that I really have to tab-dock the source files in the
2nd dock to make them readable (so I can only see one source file at a
time).
So - I’m now setup the way I like – I still have to agree with Don and
others that the UI is rather cumbersome to use but I’m happy!
If anyone cares, what I did was:
* start windbg with no params
* create two new docks (Window->Open Dock)
* Opened two of the placeholder source files from the Themes
sub-dir and tab-docked them both in one of the new docks
* Opened the disassembly display and maximized it into the 2nd new
dock
* Opened the command window & maximized it in the main windbg
window
* Opened the calls window and placed it in the bottom half of the
main window, then resized it so it only takes ~1/4 of the available
space.
* Exited windbg and saved the workspace.
Now I have something that looks a lot like the old UI
Simon
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Monday, February 21, 2005 2:57 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Disable the docking windows
Just run “WinDbg”. Then setup your UI how you want, and save it
as the base workspace. Other sessions will inherit the default
workspace. Again, Themes.doc has some more detail.
Pushing windows behind other windows can be done by using
multiple docks.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Graham, Simon
Sent: Monday, February 21, 2005 11:47 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Disable the docking windows
Maybe I havent spent the requisite amount of time on this yet,
but I do most of my debugging with dumps which means (to date at least!)
I have to customize the UI everytime I open a new dump file. I presume
it must be possible to do this once and save it as the ‘default’
workspace…
Still, I’d like source windows to be able to float and also be
able to push them behind the command window - there simply isn’t enough
real estate to use docking…
Simon
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Monday, February 21, 2005 2:12 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Disable the docking windows
These steps only need to be done once. In addition,
they seem complicated only because they are written to be generic enough
to apply to any scenario. Here’s a simpler version of them:
1 - tab-doc a source window (b.cxx) on top of another
source window (a.cxx).
After that single step, all new source windows will be
opened as tab-docked against a.cxx.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Graham, Simon
Sent: Monday, February 21, 2005 10:21 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Disable the docking windows
Well, I dont know what Tim wants but I liked the old
behaviour where I could maximize the command window, source windows
would popup up as needed but could be hidden behind the command window.
I guess I could tab-dock sources with command BUT I dont
like that either because the source windows end up maximized – it’s
nice to be able to have a few source windows show on the display and
then also be able to hide them behind the other windows.
Bottom line:
-
There should be an option to stop floating windows
being always on top
-
The description below is waaaay to complicated and
counter-intuitive to make this usable
/simgr
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Monday, February 21, 2005 1:03 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Disable the docking
windows
Is your command window taking up the entire are
of the new dock? Where do you want your source windows to go?
Do you want some form of source code to be
displayed all of the time? If no, try something like this:
-
Window –> Open Dock
-
Close all source windows.
-
Open 2 source files (or text files),
and make them float
-
Dock one of the source file into the
new dock
-
Tab-dock the 2nd source file with the
first source file
-
Feel free to close the 2nd source
file, but not the 1st source file
The instruction above will cause all source
files to open in a new dock, always tab-docked. If you want source out
of the way, just minimize that dock. Note that you can do steps 2-6
against any position in any dock, to control where source windows go
when they are opened. Again, check out themes.doc in v6.4, as it has
more information about this behavior.
Jason
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Monday, February 21, 2005 9:47 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Disable the docking
windows
Jason Shay wrote:
No. There are ways to get similar results (for
example, each window lives in its own dock), but nothing to revert to
the older style. Fe find that with multiple docks, docking windows, and
tab-docking windows, the environment can be setup to be pretty flexible.
For those who don’t want to think about it, there are pre-configured
setups available in v6.4 (see themes.doc for more info).
Although I was not the original poster, allow me
to complain about the biggest annoyance I noted in the new interface.
I like to run with the main log window docked,
so I get the maximum possible space. If I a source window pops up,
undocked, it will ALWAYS live on top of the docked window. The source
window will ALWAYS obscure the log window. I either have to minimize or
kill the source window.
That is new behavior in 6.3.
–
You are currently subscribed to windbg as:
xxxxx@winse.microsoft.com
To unsubscribe send a blank email to
xxxxx@lists.osr.com
You are currently subscribed to windbg as:
unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to
xxxxx@lists.osr.com
You are currently subscribed to windbg as: unknown
lmsubst tag argument: ‘’
To unsubscribe send a blank email to
xxxxx@lists.osr.com
You are currently subscribed to windbg as: unknown
lmsubst tag argument: ‘’
To unsubscribe send a blank email to
xxxxx@lists.osr.com
You are currently subscribed to windbg as:
xxxxx@winse.microsoft.com
To unsubscribe send a blank email to
xxxxx@lists.osr.com
You are currently subscribed to windbg as: unknown lmsubst tag
argument: ‘’
To unsubscribe send a blank email to
xxxxx@lists.osr.com
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com