| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 903.1 | | PACKED::ALLEN | Christopher Allen, Ladebug, dtn 381-0864 | Mon Mar 31 1997 11:57 | 3 |
| Can you be a little more specific about "window manager menu button" please?
-Chris
|
| 903.2 | | TLE::LUCIA | http://asaab.zko.dec.com/~lucia/biography.html | Tue Apr 01 1997 12:17 | 1 |
| The button in the upper left corner on a standard motif window...
|
| 903.3 | | TLE::JRICHARD | | Tue Apr 01 1997 14:15 | 6 |
| > The button in the upper left corner on a standard motif window...
Yes. Or really, anything that will send "close" to the window
(I think it's the WM_DELETE_WINDOW atom).
John
|
| 903.4 | | TLE::JRICHARD | | Wed Apr 02 1997 16:21 | 6 |
|
Christopher Allen pointed out to me that this only happens in FUSE!
I didn't realize that, since I'm almost always running under FUSE. :)
Thanks for the quick response!
|
| 903.5 | | PACKED::ALLEN | Christopher Allen, Ladebug, dtn 381-0864 | Thu Apr 03 1997 10:45 | 11 |
| To answer the original question: once you've closed the I/O window, there's no
way of getting it back without restarting the debugger.
There is a difference between running dxladebug standalone and running it from
FUSE. When running from FUSE dxladebug will let you close the I/O window, and
when running standalone dxladebug will NOT let you close the I/O window.
Given that you can't get it back once it's closed, I think we should fix
dxladebug so that it never lets users close the I/O window.
-Chris
|
| 903.6 | | DECCXL::OUELLETTE | crunch | Thu Apr 03 1997 19:29 | 1 |
| ... or perhaps recreate it upon rerun?
|