|Command handlers are no longer activated after migration to E4 [message #1792477]
||Wed, 18 July 2018 12:16
| Jens Kutzsche
Registered: July 2009
I have migrate a RCP application to E4. Since the migration, some command handlers that have an "enableWhen" declaration with a tester are no longer activated.
I have found that the current selection is set as a variable in an instance of the EvaluationContext by the WorkbenchSourceProvider.
In our PropertyTester implementation, however, the receiver argument in the test method is now always Null. It seems that the wrong context is used here, because the E4HandlerProxy creates always a new ExpressionContext in the method setEnabled. This is used for further processing. The method setEnabled also has an optional injection of an IEvaluationContext instance, but that is Null for us.
Did we forget something during the migration or could this be a mistake in the platform?
Powered by FUDForum
. Page generated in 0.01913 seconds