Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335323

Summary:	[Commands] Cannot save a perspective from the help center
Product:	[Eclipse Project] Platform	Reporter:	Remy Suen <remy.suen>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Remy Suen

2011-01-25 10:00:51 EST

1. Window > Show View > Other...
2. F1
3. Click the 'Displaying Views' link.
4. The help comes up
5. Click the 'Window > Save Perspective As...' link.
6. The workbench window comes back up but nothing happens.
7. An error is logged.

I would think I should be able to save a perspective as long as my workbench window is up and there's a perspective.

org.eclipse.core.commands.NotEnabledException: Trying to execute the disabled command org.eclipse.ui.window.savePerspective
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:469)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.help.ui.internal.ExecuteCommandAction.executeSerializedCommand(ExecuteCommandAction.java:115)
at org.eclipse.help.ui.internal.ExecuteCommandAction.access$1(ExecuteCommandAction.java:110)
at org.eclipse.help.ui.internal.ExecuteCommandAction$2.run(ExecuteCommandAction.java:76)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4101)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3718)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.handlers.ShowViewHandler.openOther(ShowViewHandler.java:96)
at org.eclipse.ui.handlers.ShowViewHandler.execute(ShowViewHandler.java:73)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at org.eclipse.ui.internal.ShowViewMenu$3.run(ShowViewMenu.java:187)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4126)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3715)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2697)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2661)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2495)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)

Comment 1 Paul Webster

2011-01-25 12:47:44 EST

The problem is that the dialog is up ... we might filter out the activeWorkbenchWindow in that case.

PW

Comment 2 Lars Vogel

2019-09-24 13:49:51 EDT

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.