Eclipse Community Forums: Eclipse Platform » enable command handler on startup

Home » Eclipse Projects » Eclipse Platform » enable command handler on startup

enable command handler on startup [message #332028]

Wed, 01 October 2008 11:27

Eclipse User

Hi,

I've bound a command handler to a menu in combination with the
visibleWhen option "checkEnabled". The plugin hosting the command handle
will not activated before the first command execution is triggered. This
ends into that my menu item is always enabled, independent on the state
the command handle would decide. How to I force the extension to
consider my handler right from front up. (The decision is dependent on
an value retrieved from an adapter for the current selection, where the
adapter is registered anywhere else.) And as second handicap: I'm
referring to a viewer that is not in my hand - so that I can't change
the menu initialization sequence...

Any ideas are welcome ... :-)

Sven

Re: enable command handler on startup [message #332046 is a reply to message #332028]

Wed, 01 October 2008 14:54

Eclipse User

Are you contributing your handler through org.eclipse.ui.handlers? You
can use enabledWhen and core expressions to check if objects can be
adapted using the <adapt/> element

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.platform.doc.isv/guide/workbench.htm

Re: enable command handler on startup [message #332081 is a reply to message #332046]

Thu, 02 October 2008 08:15

Eclipse User

Paul,

this delegates the problem only to the next level. The problem is
located within the plugin activation. I have an adapter factory
registered for the selection object the command shall be attached. The
handler has the enableWhen parameter set. But the adapter is not
available until the plugin is activated.

The solution was the org.eclipse.ui.startup extension that forces
equinox to load my plugin right from front up. Is it valuable to add an
expression option to the adapt parameter within the expression language?

Sven

Paul Webster wrote:
> Are you contributing your handler through org.eclipse.ui.handlers?
> You can use enabledWhen and core expressions to check if objects can
> be adapted using the <adapt/> element
>
> PW
>
>

Re: enable command handler on startup [message #332085 is a reply to message #332081]

Thu, 02 October 2008 08:35

Eclipse User

Sven Krause wrote:
> The solution was the org.eclipse.ui.startup extension that forces
> equinox to load my plugin right from front up. Is it valuable to add an
> expression option to the adapt parameter within the expression language?

The property tester "test" element has a forcePluginLoading attribute
that can force a property tester to load. I'm not a big fan, but it's
possible.

If you are going to force plugin activation using
org.eclipse.ui.startup, please make sure that you are activating a
minimal plugin with little or no UI elements in it. Once a plugin is
loaded eclipse is free to instantiate any action delegates, handlers,
and a host of other things.

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.platform.doc.isv/guide/workbench.htm

Previous Topic:	Toolbar buttons with Eclipse Look
Next Topic:	Custom install handler not getting run with Eclipse 3.4

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Apr 30 06:14:55 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter