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.

Bug 37909 - Exception when switching documents using the arrow down button
Summary: Exception when switching documents using the arrow down button
Status: VERIFIED DUPLICATE of bug 37739
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-09 16:34 UTC by _ viendu
Modified: 2008-12-22 18:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
The ide.log file. This file is 921 KB (921.86 KB, text/plain)
2003-12-18 17:42 UTC, _ viendu 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ viendu 2003-12-09 16:34:01 UTC 
Using the arrow down (one of the three arrows)
from the top right corner of the editor tab to
point to an open file/form, it generates illegal state
exception (sometimes)
Comment 1 Peter Zavadsky 2003-12-10 13:06:47 UTC 
Please, provide the stack of that exception otherwise we cant go on.
I can't reproduce it.
Comment 2 _ viendu 2003-12-16 20:28:30 UTC 
java.awt.IllegalComponentStateException: component must be showing on
the screen to determine its location
	at java.awt.Component.getLocationOnScreen_NoTreeLock(Component.java:1507)
	at java.awt.Component.getLocationOnScreen(Component.java:1481)
	at
javax.swing.plaf.basic.BasicToolBarUI$DockingListener.mouseDragged(BasicToolBarUI.java:1233)
	at java.awt.Component.processMouseMotionEvent(Component.java:5148)
	at javax.swing.JComponent.processMouseMotionEvent(JComponent.java:2779)
	at java.awt.Component.processEvent(Component.java:4901)
	at java.awt.Container.processEvent(Container.java:1569)
	at java.awt.Component.dispatchEventImpl(Component.java:3615)
	at java.awt.Container.dispatchEventImpl(Container.java:1627)
	at java.awt.Component.dispatchEvent(Component.java:3477)
	at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
	at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3215)
	at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
	at java.awt.Container.dispatchEventImpl(Container.java:1613)
	at java.awt.Window.dispatchEventImpl(Window.java:1606)
	at java.awt.Component.dispatchEvent(Component.java:3477)
[catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
	at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
	at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Comment 3 _ viendu 2003-12-16 20:33:00 UTC 
This is another exception (going along with the previous one):

java.awt.IllegalComponentStateException: component must be showing on
the screen to determine its location
	at java.awt.Component.getLocationOnScreen_NoTreeLock(Component.java:1507)
	at java.awt.Component.getLocationOnScreen(Component.java:1481)
	at
javax.swing.plaf.basic.BasicToolBarUI$DockingListener.mouseReleased(BasicToolBarUI.java:1217)
	at
java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
	at java.awt.Component.processMouseEvent(Component.java:5100)
	at java.awt.Component.processEvent(Component.java:4897)
	at java.awt.Container.processEvent(Container.java:1569)
	at java.awt.Component.dispatchEventImpl(Component.java:3615)
	at java.awt.Container.dispatchEventImpl(Container.java:1627)
	at java.awt.Component.dispatchEvent(Component.java:3477)
	at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
	at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
	at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
	at java.awt.Container.dispatchEventImpl(Container.java:1613)
	at java.awt.Window.dispatchEventImpl(Window.java:1606)
	at java.awt.Component.dispatchEvent(Component.java:3477)
[catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
	at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
	at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Comment 4 Peter Zavadsky 2003-12-17 15:01:38 UTC 
Hm, seems strange. Anyway passing to guys dealing with it.
Comment 5 _ tboudreau 2003-12-17 16:20:12 UTC 
I can't figure what that component possibly has to do with BasicToolbarUI.

Please attach your log file so we know what build you're using, etc.
Comment 6 _ viendu 2003-12-18 17:42:42 UTC 
Created attachment 12635 [details]
The ide.log file.  This file is 921 KB
Comment 7 _ tboudreau 2003-12-18 19:11:21 UTC 

*** This issue has been marked as a duplicate of 37739 ***
Comment 8 Marian Mirilovic 2004-03-16 09:44:07 UTC 
verified duplicate
by the way it's already fixed for incoming NB3.6