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 197881 - IllegalStateException: No current editor.
Summary: IllegalStateException: No current editor.
Status: RESOLVED DUPLICATE of bug 197731
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-20 04:09 UTC by stiffuser
Modified: 2011-04-29 10:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 174276


Attachments
stacktrace (1.97 KB, text/plain)
2011-04-20 04:09 UTC, stiffuser
Details
stacktrace (1.97 KB, text/plain)
2011-04-28 09:27 UTC, Egor Ushakov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description stiffuser 2011-04-20 04:09:21 UTC
This issue was reported manually by stiffuser.
It already has 2 duplicates 


Build: NetBeans IDE 6.9.1 (Build 201011082200)
VM: Java HotSpot(TM) 64-Bit Server VM, 17.1-b03-307, Java(TM) SE Runtime Environment, 1.6.0_22-b04-307-10M3261
OS: Mac OS X

Stacktrace: 
java.lang.IllegalStateException: No current editor.
   at org.netbeans.modules.viewmodel.DelegatingCellEditor.getCellEditorValue(DelegatingCellEditor.java:109)
   at javax.swing.JTable.editingStopped(JTable.java:4711)
   at org.netbeans.modules.debugger.ui.models.ColumnModels$WatchesTableCellEditor$WatchesEditorPane.processKeyEvent(ColumnModels.java:738)
   at java.awt.Component.processEvent(Component.java:6129)
   at java.awt.Container.processEvent(Container.java:2085)
   at java.awt.Component.dispatchEventImpl(Component.java:4714)
Comment 1 stiffuser 2011-04-20 04:09:25 UTC
Created attachment 107850 [details]
stacktrace
Comment 2 Egor Ushakov 2011-04-28 09:27:33 UTC
Created attachment 107992 [details]
stacktrace
Comment 3 Martin Entlicher 2011-04-29 10:55:27 UTC
Was already submitted as issue #197731.

*** This bug has been marked as a duplicate of bug 197731 ***