This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Process output is discarded when user changes debugging session.
Not only process output, but all tabs in Output window are cleared when switching session. IMO it should open another set of tabs in Output window when starting new session. As it's seems as designed functionality lower prio or change to enhancement if you think. Adding keyword UI, because it can be considered as usability issue.
Each new debugger session now opens its own Process Output and Debugger console views.
*** Issue 26206 has been marked as a duplicate of this issue. ***
The fix is quite a problem for JSP debugger, because it tries to start the debugger session several times (we don't know when the server is ready) and for each try now a new debugger console is started. Is there a way how to supress this behaviour?
OutputTabInner.closeInputOutput() seems to fail. Please evaluate.
Adding Marek to cc - he did the changes in the output window for the new winsys - Marek, any idea what's going on? Do you want to take this issue?
*** Issue 38088 has been marked as a duplicate of this issue. ***
*** Issue 30705 has been marked as a duplicate of this issue. ***
Marek, since you did the UI changes to the output window for the new window system, I'm reassigning this issue to you - it looks like something changed with the way tabs are reused, so that old debugger tabs don't stay open anymore. If you don't want it, give it back, but you can probably fix it faster since you know what you did.
*** Issue 39258 has been marked as a duplicate of this issue. ***
Could this be fixed to 3.6, it's very anoying behavior if user has to close all those opened debugger output tabs when doing some extensive debugging. There is also couple of duplicates. Thanks.
AFAIK Marek is out sick, but maybe I can take a look at it while looking at the no-output- in-sdi issue (the two are probably related). *Don't* reassign this to me yet, though :-)
*** Issue 39934 has been marked as a duplicate of this issue. ***
There are 5 duplicates. Is there any progress on this issue? Thanks.
Taking this issue.
It is a silly clash of method names, owing to the fact that the implementation of InputOutput *is* the component that displays the output. So it is checking isOpened() - testing if the TopComponent component is open in the window system - when it should be testing if the output stream is still open. This probably worked before, since each output tab was a TopComponent managed by the window system. Now, however, they're just components in a tabbed pane which extend TopComponent for legacy reasons. Should be simple enough to fix.
Fixed in trunk. Checking in src/org/netbeans/core/output/OutputTabInner.java; /cvs/core/output/src/org/netbeans/core/output/OutputTabInner.java,v <-- OutputTabInner.java new revision: 1.20; previous revision: 1.19 done Checking in src/org/netbeans/core/output/OutputView.java; /cvs/core/output/src/org/netbeans/core/output/OutputView.java,v <-- OutputView.java new revision: 1.16; previous revision: 1.15 done Processing log script arguments...
JSP folks, note: If you create the IO several times while you're polling to see if the server started, you may see sets of tabs appear and disappear as you do this. There's not going to be anything I can do about that for promo-D - winsys must be accessed from the event queue, and the showing/hiding is going to get serialized on the event queue as well. The core problem is that the implementation of InputOutput *is* the component - that's just a design bug that needs to be fixed, but requires more rewriting than is going to be possible this close to a release. I've tested switching sessions in the debugger, and the output is preserved as it should be.
Verified in dev-200402221900. Thanks Tim.
moving terminal emulator issues to terminalemulator component. To see the correct version and target milestone of this issue look at Issue Activity table.