Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
The registration creates a WrapperEditorAction, which delays loading of the code. Context-aware actions typically control their enablement, which circumvents this feature of WrapperEditorAction.
But implementor has to code some trivial boilerplate code to pick up EditorActionRegistration's attributes (name, icons, ...) into his instance. Or of course, use only a subset of EAR annotation.
The WrapperEditorAction, when activated, does not create a context-aware delegate although the delegate implements that interface.
I think that the processing should be extended to make a special case for ContextAwareActions