|Re: Handler activation [message #1696402 is a reply to message #929732]
||Tue, 26 May 2015 10:02
| Jonas Helming
Registered: July 2009
as it seems, the support for activeWhen has been replaced by the context
of the respective handler (a nice solution). However, there is currently
no way activate a handler based on the curretn perspective. Am I missing
something? If not, I would open up a BR for that.
Am 01.10.2012 um 20:08 schrieb Brian de Alwis:
> With E3.x, the handlers were in a flat global namespace, and so the
> activeWhen expressions were to figure out the most specific handler for
> the current situation (e.g., active when the activePartId = xxx).
> With E4.x, handlers can be installed on parts, windows, as well as
> globally on the MApplication. Handler look up starts from the active
> part and proceeds upwards. So many of the uses for the activeWhen
> expressions disappeared.
> Personally, I'm not too saddened to see the disappearance of lazy
> instantiation -- it's caused my projects more trouble than it's saved.
> But I can see the usefulness of supporting enablement expressions: they
> allow reusing the same handler implementation in other circumstances.
Get professional Eclipse developer support:
Powered by FUDForum
. Page generated in 0.12736 seconds