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.
When executing a web application, it is very convenient (perhaps even necessary) to see the execution window, as that is the only way to stop the server, started by the Execute action. Currently the Execution window is not opened by default which makes stopping the server inconvenient to do, and most users may will find out how the server can be stopped. Sorry for the high priority, but this is a major usability issue (and a usability regression).
Hmm, this is as design. It works the same way in the 3.3.1, or not?
Hm, I think I don't quite understand, so let's make it clear: - execution window *is not* opened on system startup and never was - execution window *is* opened when executing something (I tried simple F6 on java source and it works as expected) so, what are you trying to say? first case is as designed and second case is worksforme, so I'm closing for now. I'm convinced that this is just misunderstanding, so please explain what's wrong and reopen. Thx.
Oops, my fault, I was wrong with second case I described, I mixed execution and output window, sorry. Ok now I understand, what you say is: "Execution window should automatically open whenever execution process starts." This will require nbui attention.
To Marian: I guess I should clarify what I mean. In NB 3.3.1, the Execution window was visible after execution, as the IDE switched to the Running workspace. Now there is no Running workspace, so the execution window is not visible after execution.
Yes, Peter is right, my fault, sorry. Jano , please help us.
I already started new thread about this issue on nbui, because IMO there is ui specification missing, apparently behaviour of execution window isn't well thought out now when running workspace is in vain.
assigned to jrojcek because we need HIE/UI work. Please reassign back to dsimonek after the the info he asked for is provided.
I think this has been agreed in nbui discussion: Execution view should be opened automatically when a process is started and the view is not visible. Execution view should be closed automatically when last executed process is terminated and the view was opened automatically. It means that do not close the view automatically if it was opened explicitly.
working on it...
fixed in main trunk.
I am reopening this issue because the fix is not correct. I didn't know that internal processes like compilation are displayed in Execution view. The result is that compilation automatically opens and closes Execution view. Automatic opening should mimic switching to Execution workspace from previous release, thus Execution view should be opened *only* when execute action is run (or was there a different condition for switching to Executing workspace?). Maya, is it correct now? I am sorry for blunder. Please, implement the fix to 3.4. Thank you.
My fix is doing exactly what was specified by nbui discussion result ;-) I doubt if last specified approach is correct either - there may be processes executed directly through execution engine, not through execute action, and they will not trigger exec window opening, which is again not correct. In other words - it's not clear when exec window should be opened and when shouldn't.
I agree. How does switching to Executing workspace work in 3.3? Can we do the same but instead of switching workspace open the view?
When running NB3.3 following happens when running source that needs to be compiled first. Workspace is switched only when the source is actually run (compilation was successful). It means that Execution view should be opened only after successful compilation in case a source have to be compiled first.
Yes, right, but my complain above is still valid. What if anybody starts process using ExecutionEngine.execute?
What happened in that case in 3.3 with workspace switching? I hope we can do the same with opening the view. Does it make sense?
verified in nb3.4
Resolved for 3.4.x or earlier, no new info since then -> closing.