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.
I have just strated trying out the beta 6 version of 3.3 and have found an rather annoying bug. I use a remote CVS database and include the $data$ and $revision$ tags at the top of each of my classes. When I do a commit of *any* class with these at the top I have to shut netbeans down and restart it because I can no longer get to the form editor panel. Every time I try and switch to the the form editor panel I get and array index out of bounds exception. This happens on every commit. Cheers
Created attachment 3648 [details] ide log file
I don't think it's a javacvs issue. The problem is that since you've got the $date$ and $revision$ keyword substitutions there, the file changes upon commit and it's reloaded. reassigning to form module.
The exception looks like a window system problem...
Dafe, this one is troublesome: Sat Dec 01 15:16:06 GMT 2001: java.lang.ArrayIndexOutOfBoundsException: <no message> java.lang.ArrayIndexOutOfBoundsException at org.netbeans.core.windows.frames.SplitContainerImpl.componentFocusGained(SplitContainerImpl.java:825) at org.netbeans.core.windows.frames.DefaultContainerImpl.eventDispatched(DefaultContainerImpl.java:935) at java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:1521) at java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:1433) at java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:1432) at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:1390) at java.awt.Component.dispatchEventImpl(Component.java:2507) at java.awt.Container.dispatchEventImpl(Container.java:1213) at java.awt.Component.dispatchEvent(Component.java:2497) at java.awt.LightweightDispatcher.processFocusEvent(Container.java:2167) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2130) at java.awt.Container.dispatchEventImpl(Container.java:1200) at java.awt.Window.dispatchEventImpl(Window.java:926) at java.awt.Component.dispatchEvent(Component.java:2497) at java.awt.EventQueue.dispatchEvent(EventQueue.java:339) [catch] at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
reassigned to Marek, has connection wiht his bugfix #16631, which would need to be improved.
Yes it is connected with fix of issue #16631. I keep reference on top component requested by requestVisible(). Problem is when this top component is removed from container before frame on which requestVisible() was called (Form mode in this case) is activated. (It is removed for example by Form Editor when its source is externally modified by for example CVS. Actually Form Editor replaces instance of FormDesigner by new instance.) So I had to add additional check if requested top component is still present in container and if not I set it to focused top component. Fixed in branch release33, pending for branch release330.
I add steps to reproduce this bug: 1. Open two forms in Form Editor. 2. Select Source Editor. Switch between tabs. It causes call of requestVisible() on Form mode. You can see that tabs in Form are switched too according to selected tab is SourceEditor. 3. Now externally modify source selected in Source Editor. It causes replacing instance of FormDesigner in Form mode as soon as IDE detects change. 4. Select Form mode. It causes ArrayOutOfBoundsException.
Created attachment 3685 [details] patch18251.jar
Attached patch can be used for beta6 build.
Please, Graham, check that it solves problem with beta6 build.
Patch verified.
verified that it works ok in release33, on win2k.
mslama already committed the fix into release330
marking as verified
Just like to say thanks and that it works. Cheers
*** Issue 17441 has been marked as a duplicate of this issue. ***
*** Issue 17935 has been marked as a duplicate of this issue. ***
Resolved for 3.4.x or earlier, no new info since then -> closing.