Handler enablement spreading across plugin.xml and Java code? [message #323975] |
Tue, 15 January 2008 04:57  |
Eclipse User |
|
|
|
How to deal with the possibility that the enabled state of a handler
depends both on the selection (as expressed in a core expression) and
some other application state that cannot be expressed using a core
expression? I noticed that #isEnabled still gets called after the core
expression evaluates to true, so my implementation of #isEnabled takes
this other app state into account. All works as it's supposed to, but I
find it rather ugly that my logic determining enablement is now
partially in plugin.xml and partially in the handler's code.
Is there a better of way of doing this?
Thanks all,
Jasper.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03643 seconds