Description David Gonzalez 2016-02-03 09:56:02 EST

Hi there,

our product is based on Eclipse RCP and we have a problem we couldn't solve yet after a migration from Eclipse 3.7.2 to 4.5.1.

When calling command the trigger gets lost. Here is an example of the code we run to programmatically call a command:

ICommandService cmdService = (ICommandService) PlatformUI.getWorkbench().getActiveWorkbenchWindow().getService(ICommandService.class);
Command cmd = cmdService.getCommand("commandId");
Parameterization param = new Parameterization(cmd.getParameter("parameterId"), "value");
ParameterizedCommand pc = new ParameterizedCommand(cmd, new Parameterization[] { param });
pc.executeWithChecks("Trigger", null);

In version 3.7.2 the handler gets the ExecutionEvent with the correct trigger object in its execute-Method. In version 4.5.1 the trigger in the ExecutionEvent is always null.

We need to set the trigger to determine who called the handler if it's called programmatically.

Hope you can help us with that!
David