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.
Using Netbeans 3.4.1 in MDI mode and Apple's JDK 1.4.1, the main Netbeans frame cannot be made smaller. It can be made larger. Sometimes if it is made larger, this size sticks and it can't be returned to its initial size. It never can be made smaller than its startup size. This happens whether or not apple.awt.showGrowBox is true. The separate windows in SDI mode will resize (larger and smaller), except for the main toolbar frame. It has a problem similar to the main MDI frame, except that it only applies horizontally -- you can make it wider but not narrower. This happens when there is clearly enough dead space that resizing should be allowed. This issue did not exist in Apple's JDK 1.3 in MDI mode. I don't know about the SDI behavior as I never used SDI until this MDI bug arose with 1.4. I am using the release version of 3.4.1 and launching from NetbeansLauncher with the following settings: L&F: Default (which turns out to be Metal) Live resizing of windows: off Extra parameters: -J-Dapple.awt.showGrowBox="true" -J-Dapple.awt.antialiasing="false" -J-Dapple.awt.textantialiasing="false" Switching to the aqua L&F (using -ui apple.laf.AquaLookAndFeel) doesn't affect this issue. Since it didn't happen in 1.3, it is possible that this is not a Netbeans bug, but I have not seen it in any other java applications. For the record this is on OS X 10.2.4 with Apple's JDK 1.4.1 (Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-39), according to java -version). The machine is a 1GHz flat-panel iMac with 1GB of RAM.
reassigne to Tomas H. for investigation
It seems to me that this is caused by interaction between NetBeans new JDK 1.4.1. This is still broken with NB 3.5. :-(
For workaround seekers, see the nbusers thread that contains this message: http://www.netbeans.org/servlets/ReadMsg?msgId=512216&listName=nbusers It's not a full workaround, but it's a temporary solution until this issue is resolved.
It is JDK bug and hopefully will be fixed in next JDK update from Apple.
Fixed by Java 1.4.1 Update 1
rsutphin, could you please verify with new jdk ? thanks advance.
closed