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 remember fixing this (or at least surpressing the exception) in the old button of CloseButtonTabbedPane. It's an event-ordering problem that Swing does not handle well. The code to deal with this should already be in cvs history in output2's version of CloseButtonTabbedPane and should be simple to port. java.awt.IllegalComponentStateException: component must be showing on the screen to determine its location at java.awt.Component.getLocationOnScreen_NoTreeLock(Component.java:1678) at java.awt.Component.getLocationOnScreen(Component.java:1652) at javax.swing.JPopupMenu.show(JPopupMenu.java:950) at org.netbeans.core.output2.Controller.postPopupMenu(Controller.java:896) at org.netbeans.core.output2.OutputWindow.postPopupMenu(OutputWindow.java:259) at org.netbeans.core.output2.OutputTab.postPopupMenu(OutputTab.java:154) at org.netbeans.core.output2.OutputPane.postPopupMenu(OutputPane.java:65) at org.netbeans.core.output2.ui.AbstractOutputPane.mousePressed(AbstractOutputPane.java:534) at org.netbeans.core.output2.OutputPane.mousePressed(OutputPane.java:148) at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:222) at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:221) at java.awt.Component.processMouseEvent(Component.java:5551) at javax.swing.JComponent.processMouseEvent(JComponent.java:3126) at java.awt.Component.processEvent(Component.java:5319) at java.awt.Container.processEvent(Container.java:2010) at java.awt.Component.dispatchEventImpl(Component.java:4021) at java.awt.Container.dispatchEventImpl(Container.java:2068) at java.awt.Component.dispatchEvent(Component.java:3869) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4256) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3933) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3866) at java.awt.Container.dispatchEventImpl(Container.java:2054) at java.awt.Window.dispatchEventImpl(Window.java:1774) at java.awt.Component.dispatchEvent(Component.java:3869) [catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:463) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176) at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
not output related, output2 now uses the shared CloseButtonTabbedPane from openide/awt. reassigning
Tim, could you write steps for reproduction, if they exists? I searched old CloseButtonTabbedPane in cvs history and didn't find any code that catches mentioned exception. Only code I found is protected void processMouseEvent (MouseEvent me) { try { super.processMouseEvent (me); } catch (ArrayIndexOutOfBoundsException aioobe) { //Bug in BasicTabbedPaneUI$Handler: The focusIndex field is not //updated when tabs are removed programmatically, so it will try to //repaint a tab that's not there Exceptions.attachLocalizedMessage(aioobe, "Suppressed AIOOBE bug in BasicTabbedPaneUI"); //NOI18N Logger.getAnonymousLogger().log(Level.WARNING, null, aioobe); } starting at line 360, but I guess it's not the right piece. Anyway, passing to Standa who did move of CloseButtonTabbedPane.
i thought i'd refactored the complete closebuttontabbedpane out to openide/awt but i'll check the cvs history
there's no closebuttontabbedpane in the stack trace, milosi, pls re-evaluate, thanks.
output -> t_h
Is it possible to reproduce this bug?
Same error is mentioned in 119409 and 129756. Btw i never was able to reproduce this.
In every one of these cases, a component is trying to respond to a mouse event after a previous mouse listener hid the component. The solution might be as simple as to ensure that any mouse listeners that affect the component hierarchy call consume() on the mouse event they're handling - at least in theory that should stop further processing of the event.
*** This issue has been marked as a duplicate of 137370 ***