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.
[ JDK VERSION : 1.6.26 ] Steps to reproduce: 1) maximize the editor window; 2) click on the projects 3) choose project and on the context menu choose New and try to add file, nothing happens please refer to video, that illustrates problem: http://goo.gl/z3qJT Thanks, Medea
Netbeans Build 201109090600
I cannot reproduce it - I tried linux, windows and Mac. It's only with new servlets or it is a problem with any new, like new class in java projects? Does it work when you use shortcuts (ctrl + n) or file menu? I don't think it's P2, it's just a minor bug and it's working for me. -> P4
Still same thing with new nightly build: Product Version: NetBeans IDE Dev (Build 201109110600) Java: 1.6.0_26; Java HotSpot(TM) 64-Bit Server VM 20.1-b02-384 System: Mac OS X version 10.6.8 running on x86_64; Nothing works in context menu e.g. clicking on build does nothing, etc. So far I have no problem neither with shortcurts nor with menu. Previously installing new version of netbeans i have deleted dev in the /Users/medea/.netbeans/ Thanks, Medea
Just to clarify a little bit, in case video will be removed, by editor i mean source editor. Also maybe it is not blocker or critical issue but at least i think it is major (P3) not minor (P4). Thanks, Medea
The same goes for the all actions in Versioning main menu: 1) Minimize the window group with the Projects View 2) Close all editors 3) Now go to the projects view, select a mercurial project 4) Now click on the Main menu: Team, all actions are disabled IMO the main menu steals focus from the Projects view and the selected nodes are immediately changed to an empty selection
Have checked Build 201109132156 Seems like it no longer the issue, ovrabec, does it also works for you? Thanks, Medea
It seems to be solved now. I use Build 201109132156.
Solved or not? If not, please show stacktraces of selected nodes being changed.
yep, it works correctly again.
*** Bug 209971 has been marked as a duplicate of this bug. ***