The following patch is needed to DebuggerWindow:
Index: src/org/netbeans/modules/debugger/support/nodes/DebuggerWindow.java
===================================================================
RCS file:
/cvs/debuggercore/src/org/netbeans/modules/debugger/support/nodes/DebuggerWindow.java,v
retrieving revision 1.16
diff -c -r1.16 DebuggerWindow.java
*** src/org/netbeans/modules/debugger/support/nodes/DebuggerWindow.java	10 Nov 2001 02:55:32 -0000	1.16
--- src/org/netbeans/modules/debugger/support/nodes/DebuggerWindow.java	15 Nov 2001 00:00:27 -0000
***************
*** 465,470 ****
--- 465,477 ----
                  initSpecialViews (v, c);
              }*/
                  
+ 	    // Ensure that the component is not hidden. This happens when
+ 	    // components are closed as part of a dock-into-debugging window
+ 	    // operation.
+             if (!c.isVisible()) {
+ 		c.setVisible(true);
+ 	    }
+ 	    
              if (c instanceof ToolbarView) {
                  relToolbar = false;
                  ((ToolbarView) c).setOrientation (


That's because sometimes moving a component away from a tabbed window
and into the debuggerwindow causes the component to be called with
setVisible(false) (the tab manager ui is doing this) so by similar reasoning
the new manager, the DebuggerWindow, should make the views visible.

Note that this will be a no-op in most cases since generally views haven't
been made hidden by some prior window operation - thus it's low risk
for you. And in the cases where isVisible() is false, you -want- the above
setVisible(true).