Community
Participate
Working Groups
I have a view extension that implements the init method. In some cases, it throws a PartInitException exception. However, this exception does not arrive at the caller of IWorkbenchPage.showView. Instead, showView returns an object of type org.eclipse.ui.internal.ErrorViewPart. Given that showView is declared with a 'throws' clause of PartInitException, this seems wrong.
If PartInitException is thrown during init, it should get propagated to the caller of openEditor rather than opening the error view. Stefan, I thought this was addressed in 3.1. Do you recall where we ended up on this?
To be perfectly clear, there's no openEditor involved here (in my code). My IEditorActionDelegate contains the following, and gets back the error view instead of catching the error. IViewPart view; try { view = PlatformUI.getWorkbench().getActiveWorkbenchWindow(). getActivePage().showView("com.basistech.extarbl.gui.text_word_analysis"); } catch (PartInitException e) { /*...*/ }
Sorry, I ment showView. It's actually the same case for openEditor.
Once the error view object comes into existence, it gets harder and harder to control the UI, since showView then simply shows it without attempting to rerun the initialization.
Turns out this wasn't addressed in 3.1 due to high risk of the proposed fix, late in the game. For history, see bug 90582 comment 4 and later.
*** Bug 102309 has been marked as a duplicate of this bug. ***
Folks, Could you do me a favor and tell me how to programmatically close the error view? I'm feeing quite dense, but I can't seem to find the API for closing views (as opposed to editors) anywhere. If I have that information I can work around this problem fairly easily. --benson
IWorkbenchPage.hideView(IViewPart).
Thanks.
Is this still a problem in 3.3? PW
Changes requested on bug 193523
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
