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.
I have mapped F6 to Execute Project (Ctrl Shift F6 is still assigned) and have selected the main class for the project. I compile something with F9, after compilation the Output Window is selected, when I hit F6 or Shift-Ctrl-F6 nothing happens. If I select another window, F6 works.
you must choose the editor pane or the node of the class you want to execute. If the focus is elsewhere how the IDE can know what you want to execute?
*** Issue 18549 has been marked as a duplicate of this issue. ***
I am using the "execute project" not "execute" command from the keyboard. It should not matter which window I have active. I have a project main class and that is the one that should be run. This used to work and it was only when I went to 3.3 rc1 did I notice this "bug." It now happens in the proper release also. It is annoying because I am used to pressing F9 then shift-ctrl-F6 (or just F6 since I have changed that to "execute project"). Now, I often press F9, have to click, say on the editor window with a non- main class in the window, then press F6 and the main class is executed. It happens when I get a couple of Note: lines in the output window, a deprecation warning in my case; the output window is then made active. So it matters which file I am pressing F9 for despite the fact that it does compile correctly. It is not consistant. I don't mean to be picky, I think that netbeans is a fantastic development environment.
Passing to Ales to check if terminal emulator can somehow involve this. Feel free to reassign accordingly.
Strange, I cannot reproduce this behaviour - it worjks fine for me. Could you please once again describe reproducing steps? Thanks.
Great! Now I can't reproduce it at will, damn. This has been bugging me for days. I think that the Note: warnings were a red herring as it is currently working fine. Do you want to suspend this and I will add another note when I can reliably reproduce it?
Sure, I'm marking it as WORKSFORME, so if you reproduce it again, feel free to REOPEN it :-)
verified
Resolved for 3.4.x or earlier, no new info since then -> closing.
moving terminal emulator issues to terminalemulator component. To see the correct version and target milestone of this issue look at Issue Activity table.