|Core expressions framework behaviour [message #673919]
||Wed, 25 May 2011 07:31
| David Pérez
Registered: July 2009
One thing I have detected when I have switched to the commands framework, and used enabledment expressions is this:|
I have some expressions that depend on the current selection in many views.
If the selection changes in a single view, the ISources.ACTIVE_CURRENT_SELECTION_NAME property fires as changed for ALL the views, included the ones in other perspectives, even if their selection isn't changed.
This is due to the fact that variables in the evaluation framework are considered global.
Invoking TableViewer#getSelection(), provokes refreshing the text of the columns. In some of my views it can raise an error condition. That's why I have detected this behaviour. I think just getting the current unchanged selection wouldn't need to refresh the text of the cells.
I consider this not to be very efficient.
I'm considering not to use expressions in my commands.
What do the experts think about this?
Powered by FUDForum
. Page generated in 0.02408 seconds