Community
Participate
Working Groups
1. Start a fresh e4 workbench 2. Detach the Javadoc view by dragging it off the workbench window 3. Close the detached stack Result: Error dialog for the following exception: !ENTRY org.eclipse.e4.ui.workbench 4 0 2010-07-16 14:29:17.792 !MESSAGE Internal Error !STACK 0 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.widgets.Widget.error(Widget.java:468) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340) at org.eclipse.e4.ui.widgets.CTabItem.isShowing(CTabItem.java:261) at org.eclipse.e4.ui.widgets.CTabFolder$3.getLocation(CTabFolder.java:1106) ... at org.eclipse.swt.widgets.Control.setSavedFocus(Control.java:3269) at org.eclipse.swt.widgets.Decorations.restoreFocus(Decorations.java:821) at org.eclipse.swt.widgets.Decorations.WM_ACTIVATE(Decorations.java:1639) at org.eclipse.swt.widgets.Shell.WM_ACTIVATE(Shell.java:2114) ...
I suspect that this is (will be) fixed in the next build. This was the result of the new CTF code that moves stack's toolbars down to the next line if there's not enough space on the top line. Please retry with today's build and ping back if there is still an issue.
I currently get this bug with CVS HEAD.
Did you use the red 'x' to close or did you close the view ? There are different issues depending on the path. Btw, I've just checked a fix to some bogus code in the PartRenderingEngine as regards DW's. With this change the scenario seems to work for me if I close the view, not the shell. I'm looking into how to 'wire off' the close button now...
I used the button of the surrounding window (i.e. the Microsoft Windows button, not the button on the tab item).
Stefan, first off thanks *huge* for doing this, you've already caught a number of regressions !! If you synch up you should find that the red 'x' is gone from DW's now...could you retest and close this (as a DUP of 320097) if it's working now?
*** This bug has been marked as a duplicate of bug 320097 ***