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.
Sun JDK 1.4.1, fresh install of NB 3.4. Created a new GUI form with wizard, opens fine. Closed form editor, tried to reopen, but form editor does not reappear. Hunted around, found that the form editor was opened in the Editing workspace instead. Went to Tools | Options | IDE Configuration | Look and Feel | Workspaces | GUI Editing | Form Editor and noticed that its bounds looked suspicious: had a negative number in there. Went and copied the Bounds values from the Form Editor entry in the Editing workspace, pasted them here, then Form Editor showed up properly in GUI Editing workspace.
Forgot to mention: I wonder if this is related to issues 27439 and/or 26095? Also, no messages in ide.log or console when this happens.
*** This issue has been marked as a duplicate of 23163 ***
Reopening, pzavadsky thinks this is not duplicate of 23163.
Reasigning to core/winsys. It looks like the size of the form mode gets screwed (so it opens with zero size). The workaround is to delete win sys config data, or to maximize the windows on desktop. People often complain about it, both in NB 3.4 and NB 3.4.1, e.g.: http://www.netbeans.org/servlets/ReadMsg?msgId=375664&listName=nbusers http://www.netbeans.org/servlets/ReadMsg?msgId=465365&listName=nbui http://www.netbeans.org/servlets/ReadMsg?msgId=467056&listName=nbusers Is this know issue? Some fixes in this area already done?
I decrease priority -> it is random, and I didn't get any report of this issue against the dev builds. Anyway I was asked to provide some sanity check when reading the values from layer, and repair them to some defaults in case they are negative. So I'm going to check the code.
Hm, when I've seen the image, it reminds me something, but I can't remember what was the problem and if and how was fixed. Will try to search a bit.
Fixed in [trunk] core/../windows/layers/ModeData.java 1..108 Note: The fix is just a sanity check when deserializing the bounds values, if invalid (negative) or small (in case of normal bounds, width or heigth < 30) then are set to some defaults and it is logged.
Slightly refined fix: core/../windows/layers/ModeData.java 1.109
verified in [nb_release35](20030317)