Community
Participate
Working Groups
I get the following stack trace in Eclipse 4.6.2: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(Unknown Source) at org.eclipse.swt.SWT.error(Unknown Source) at org.eclipse.swt.SWT.error(Unknown Source) at org.eclipse.swt.widgets.Widget.error(Unknown Source) at org.eclipse.swt.widgets.Widget.checkWidget(Unknown Source) at org.eclipse.swt.widgets.Widget.isListening(Unknown Source) at org.eclipse.swt.custom.StyledText.modifyContent(Unknown Source) at org.eclipse.swt.custom.StyledText.sendKeyEvent(Unknown Source) at org.eclipse.swt.custom.StyledText.doContent(Unknown Source) at org.eclipse.swt.custom.StyledText.handleKey(Unknown Source) at org.eclipse.swt.custom.StyledText.handleKeyDown(Unknown Source) at org.eclipse.swt.custom.StyledText$7.handleEvent(Unknown Source) at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source) at org.eclipse.swt.widgets.Display.sendEvent(Unknown Source) at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Unknown Source) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Unknown Source) at org.eclipse.swt.widgets.Widget.wmChar(Unknown Source) at org.eclipse.swt.widgets.Control.WM_CHAR(Unknown Source) at org.eclipse.swt.widgets.Canvas.WM_CHAR(Unknown Source) at org.eclipse.swt.widgets.Control.windowProc(Unknown Source) at org.eclipse.swt.widgets.Canvas.windowProc(Unknown Source) at org.eclipse.swt.widgets.Display.windowProc(Unknown Source) at org.eclipse.swt.widgets.HookableDisplay.windowProc(HookableDisplay.java:56) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(Unknown Source) at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) at de.ikoffice.gui.MainWindow.open(MainWindow.java:1824) I checked the latest version and there has no widget-disposed-checking been added since my version, so I believe the bug should occur also on later and earlier versions. I kindly request to add some error checking here.