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.
Created attachment 125054 [details] Form files in projects view NetBeans IDE 7.3 Beta (Build 201209232010) JDK 7u7 64-bit At times the .form files for JPanel forms are appearing in the projects view where I would not have expected them to. When I started the IDE, only the .java files were shown. And later on I noticed that the .form files are also appearing (see screenshot). I don't know what the cause could be yet, but will keep my eye on it.
Same problem occured at my pc. Some additional informations: -) this occurs at all form-files. Not only JPanel and really at all gui´s in the project. -) Occured at the current build: .. Product Version: NetBeans IDE Dev (Build 201209260001) Java: 1.7.0_07; Java HotSpot(TM) 64-Bit Server VM 23.3-b01 System: Windows 7 version 6.1 running on amd64; Cp1252; de_AT (nb)
Created attachment 125055 [details] Log-File. (but there´s no exception)
I just created a new panel in the same project shown in the screenshot, and it is displayed as it should be.
there is an exception in your log file: Caused: java.lang.Error: java.beans.IntrospectionException: Method not found: setFixedColCount at Softline.awt.ColumnFixScrollPaneBeanInfo.getPropertyDescriptors(ColumnFixScrollPaneBeanInfo.java:69) at java.beans.Introspector.getPropertyDescriptors(Introspector.java:609) at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:450) at java.beans.Introspector.getBeanInfo(Introspector.java:416) at java.beans.Introspector.getBeanInfo(Introspector.java:161) at org.openide.util.Utilities.getBeanInfo(Utilities.java:400) [catch] at org.netbeans.modules.form.FormUtils.getBeanInfo(FormUtils.java:1812) I am not sure how it relates to missing icons, but I'd rather have a reproducible case without errors. Anyway, next time you see the duplicated form files, take a heap dump. Log file is not enough.
It's a known problem that this is happening, but there are no good known steps to reproduce. If you see it again, please take a heap dump as suggusted by jtulach. (The exception in the log file is unrelated to this problem and is handled well.) *** This bug has been marked as a duplicate of bug 202614 ***