| [e4-dev] Model events and rendering... |
The order in which our event handlers get notified of events are not exactly deterministic at the moment.
<rcjsuen> tjwatson: whoops, i mean to say the event handlers that get notified
<tjwatson> ah, I think we simply use service ranking order for that
This causes problems between what someone's EventHandler might expect versus reality.
For example, we have handlers in our stack renderers that creates the element only when they become the selected element. This is [only interesting] for stacks to support lazy-loading requirements.
However, someone's handler may be notified of a selection change before the renderer gets to it so if the handler asks for the element's widget or implementing object, 'null' will be returned. Moments later, the renderer's handler gets notified and the element gets instantiated. Any handler that gets notified is okay but the ones that got notified before are out of luck.
It seems that the addons may be the ones that are most likely to be susceptible to this problem as they are created before the rendering engine gets created.
Please provide your thoughts on the bug below. Thank you.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=340771
Regards,
Remy
----------
Remy Suen
Eclipse Platform/UI Committer
IBM Ottawa
1-613-356-5162