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 been using Netbeans since february 2007, following its long path to become a mature IDE for Ruby on Rails. Most of the time, I have used the latest build, reported some issues and it has been a fun and productive experience. However, I am feeling a bit frustrated now, because of some recent changes in the behavior of the Output Window(CTRL+4) . I rely highly on Autospec to run my unit tests. With Netbeans 6.5, I have the code on one widow and I use an undocked Output window on the right side in order to check out the tests results and open classes in 1 click. This is very handy because Netbeans opens the guilty class in the main window, at the exact location of the guilty line of the backtrace. This makes the whole development cycle "super" productive! Since Netbeans latest build 23rd of March 2009 (7.0?), this behavior has changed. It seems that the Output window behaves like any other window. By default, it opens in a normal tab, forcing you to constantly CTRL+TAB to switch between classes and output. If you undock it and you click on a backtrace, it will open it in the same undocked window as the Output!!! So unless you move theses windows to the main IDE, there is no way you can compare the tests output and the class itself. As far as I am concerned, this is a serious usability issue and I'd like to discuss it with other netbeans users and netbeans IDE developers. In the following screenshot, you can see that every time I click on a backtrace, it opens the window in a tab next to the Output window .... Please, please rollback the Output Window to its previous behavior! Screenshots: http://21croissants.blogspot.com/2009/03/netbeans-usability.html I have also posted a message in the Netbeans mailing list to discuss this issue: http://www.nabble.com/Output-Window-behavior-with-Autotest---Autospec-td22663116.html
I guess my description was not clear enough so I made a screencast which illustrates the Netbeans ruby latest build behavior: http://21croissants.com/files/netbeans-ruby_usability.html
The comment in http://www.netbeans.org/issues/show_bug.cgi?id=161070 solved my problem!!! In fact, I had to delete the whole ~/.netbeans folder to solve it. Simply delete the config/Windows2Local/Components/output.settings did not work in my case