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.
This is a fairly harsh bug. I just installed NB7.1 on my OS X Lion, having used 7.0 since release. When I go into Full Screen Mode, the menu bar (not just the icons, but the actual text menu at the top of the screen) disappears and cannot be accessed. Furthermore, NB takes complete focus of the user input and it is not possible to command-tab into another application. This essentially means that NB7.1 takes over the screen and won't let the user do anything. I had to do a hard reboot to fix this and it happened a second time when I checked if this was an isolated incident. Please fix!! (A workaround at this stage would also be greatly appreciated)
Workaround: Ctrl-Shift-Return enters AND exits from fullscreen mode. But Fullscreen mode is currently defunct as all the functionality of the menu bar is hidden (and cannot be accessed even by mousing to the top of the screen)
Reassigning to Standa for evaluation
i've disabled full screen action on mac os x until there's better support for full screen applications in JDK 7 core-main ecaf6be41d04
Integrated into 'main-golden', will be available in build *201201250600* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/ecaf6be41d04 User: S. Aubrecht <saubrecht@netbeans.org> Log: #207576 - don't allow full screen on Mac OS X
The response has been a bit bizarre - instead of fixing the problem for OS X Lion, you're actually disabling fullscreen altogether? I'm sticking with 7.0 until this gets fixed!!
Product Version: NetBeans IDE 7.1.1 (Build 201202092200) JDK 7 build 228 (Developer Preview) System: Mac OS X version 10.7.3 running on x86_64; MacRoman; en_US (nb) Full screen is with this builds of JDK and NB enabled, but works as described: - menu bar disappears - it's not possible to commad-tab another application Workaround Ctrl-Shift-Return works for me, repeatable.
Product Version: NetBeans IDE Dev (Build 201202080400) Java: 1.6.0_29; Java HotSpot(TM) 64-Bit Server VM 20.4-b02-402 System: Mac OS X version 10.7.3 running on x86_64; MacRoman; en_US (nb) In JDK 6, fix is OK, Full Screen is disabled. But if you run IDE with JDK 7, open some project and if you several times pushes shortcut for Full Screen (Ctrl-Shift-Return) the exception NullPointerException at org.openide.awt.MenuBar.processKeyBinding shows up ( http://statistics.netbeans.org/analytics/detail.do?id=182544 ). (and Full Screen is still disabled, of course) So, I'm not sure if it's bug of IDE (and Reopen this Issue) or if it's bug of JDK and give Verified to this Issue...
i've enabled full screen mode for JDK version 1.7 update 4 in core-main 27a87fc3e0d3
and in release71_fixes branch as 4d8c8290dbdf
my last fix actually doesn't work so the proper one in release71_fixes is 3e065679782a (and bc2419f3bf35 to increment spec version)
Ok, means we need to rebuild RC1 ? ... I even do not see the previous in current build http://hlemyzd-2.cz.oracle.com:8080/hudson/view/All/job/NB-7.1_fixes/22/
I'm seeing a lot of talk about Java 7. Can somebody please describe what this means for the majority of users on OS X who are running Java 6 (1.6.0_29)? Please bear in mind that Java 7 isn't even officially available for OS X yet. Can't you fix this for Java 6 users? NetBeans 7.0 works great in fullscreen. DISABLING FULLSCREEN IS NOT A FIX.
we cannot fix something that is broken in JDK. disabling the action is still better than leaving users locked in full screen mode where they wouldn't know how to switch back. it should be fixed in JDK 1.7 udpate 4 developer preview that will be available in april (i think).
But this isn't a JDK problem - this isn't even anything to do with my original bug report! I haven't even got Java 7. I am a long-time Netbeans user (and developer) and I have used NetBeans 7.0 on OS X Lion since Lion was released with no problems whatsoever, in fullscreen mode. When I upgraded to NetBeans 7.1, fullscreen mode was broken to the extent that I had to reboot my machine. Disabling fullscreen mode is not a "fix" - it is disabling a key feature of the NetBeans IDE. If you want to turn this issue into a compatibility problem with Java 7, then fine, but I will have to open a new issue which addresses the original bug.
(In reply to comment #14) > > If you want to turn this issue into a compatibility problem with Java 7, then > fine, but I will have to open a new issue which addresses the original bug. open a new issue please and leave this one closed
(In reply to comment #14) > > When I upgraded to NetBeans 7.1, fullscreen mode was broken to the extent that > I had to reboot my machine. you can hide all toolbars, maximize the window and you'll get 'full screen' as implemented in netbeans 7.0
I have create a new issue #208385 to track my original bug report. @saubrecht, your suggested workaround does not work like NB7.0 fullscreen mode. In OS X, the fullscreen mode hides the window title. OS X "maximise" (green window button) does not do this.
(In reply to comment #17) > @saubrecht, your suggested workaround does not work like NB7.0 fullscreen mode. > In OS X, the fullscreen mode hides the window title. OS X "maximise" (green > window button) does not do this. right, so the only difference is 15 pixels worth of extra vertical space:)
in Product Version = NetBeans IDE 7.1.1 RC1 (Build 20120214-bc2419f3bf35) (#bc2419f3bf35) Operating System = Mac OS X version 10.7.3 running on amd64 Java; VM; Vendor = 1.7.0_04-ea; Java HotSpot(TM) 64-Bit Server VM 23.0-b14; Oracle Corporation is fullscreen enabled, and waiting for fix on JDK side. in Product Version = NetBeans IDE 7.1.1 RC1 (Build 20120214-bc2419f3bf35) (#bc2419f3bf35) Operating System = Mac OS X version 10.7.3 running on x86_64 Java; VM; Vendor = 1.6.0_29; Java HotSpot(TM) 64-Bit Server VM 20.4-b02-402; Apple Inc. is fullscreen not allowed (with proper info)
Integrated into 'releases', will be available in build *201202141413* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/4d8c8290dbdf User: S. Aubrecht <saubrecht@netbeans.org> Log: #207576 - allow Mac OS X full screen only on JDK 1.7u4
enabled native full screen support for lion in core-main 329f9485189e
@saubrecht could you please clarify what the patch means for the majority of OS X Lion users? i.e. those running the default (i.e. Java 6) JDK?
transplanted to release71_fixes branch as 93bdc43426e4 and cb7c7d4af428
(In reply to comment #22) > @saubrecht could you please clarify what the patch means for the majority of OS > X Lion users? i.e. those running the default (i.e. Java 6) JDK? that netbeans will have 'full screen' button in its main window header just like e.g. safari browser
@saubrecht, excellent, then the original bug report has finally been addressed!
*** Bug 208385 has been marked as a duplicate of this bug. ***
(In reply to comment #25) > @saubrecht, excellent, then the original bug report has finally been addressed! fommil forgot to use nice words like : Thank you very much saubrecht and I am sorry for all my exclamation marks.
Integrated into 'main-golden', will be available in build *201202240400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/1ad5c140f181 User: S. Aubrecht <saubrecht@netbeans.org> Log: #207576 - version number of JDK 1.7 dev preview has _ea suffix
Integrated into 'releases', will be available in build *201202242200* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/93bdc43426e4 User: S. Aubrecht <saubrecht@netbeans.org> Log: #207576 - enable native full screen support on mac os x lion
verified in 7.1.1 + patch 1 Product Version: NetBeans IDE 7.1 (Build 201112071828) Java: 1.6.0_29; Java HotSpot(TM) 64-Bit Server VM 20.4-b02-402 System: Mac OS X version 10.7.3 running on x86_64; MacRoman; en_US (nb) User directory: /Users/tomas/.netbeans/7.1 Cache directory: /Users/tomas/.netbeans/7.1/var/cache
The new fullscreen mode is excellent, just tried it out, thanks all!
I just spotted that there might be a bug in the new OS X fullscreen mode in NB-7.1.1 - there is a bar along the bottom of the screen which is about the same height as the (hidden) menu bar which is not doing anything. It looks like the bar at the bottom is also suffering from rendering artefacts. Is Netbeans perhaps not aware that it has more window to draw to?
(In reply to comment #32) > I just spotted that there might be a bug in the new OS X fullscreen mode in > NB-7.1.1 - there is a bar along the bottom of the screen which is about the > same height as the (hidden) menu bar which is not doing anything. > > It looks like the bar at the bottom is also suffering from rendering artefacts. > Is Netbeans perhaps not aware that it has more window to draw to? i'm aware of it. there's no bottom bar when running under JDK 1.7 though
I'm really disappointed by the way this bug is fixed. Now instead of restoring the intended (or is it?) behaviour, NetBeans now no longer has its own fullscreen mode. Instead, a new Space is created in which the application takes the entire screen (as all Lion fullscreen apps do). This means that, when working on a project, repeatedly switching between NetBeans and a browser means constant sideways animated 'swipes' of the entire screen. And I switch a lot between editor and browser. In NetBeans 7.0 it's an easy behaviour: I can have Netbeans set to fullscreen and with cmd-tab make my browser appear or disappear on top of the Netbeans window. I also have access to my Dock to switch to or open another app. This works very well for me. But when NetBeans takes up a whole other Space, the switching between apps is slower, I cannot have another texteditor on top of the NetBeans window for small notes (or whatever), and the Dock is gone. I can understand the addition of the Lion-fullscreen button, but I don't consider it an equal to the old NetBeans-fullscreen mode. And I can't image being the only one who feels this way. It's a step down in usability and a reason to stick with 7.0.