Community
Participate
Working Groups
Every WWinPluginAction registers itself as a SelectionListener,and, when it recieves a selectionChanged event, it goes and calculates its enablement although the end-user has no way to invoke such the action which means calculating enablement is unnecessary at all. This causes performance problems for enviroenment with large number of object-contribution actions and when a large number of elements are selected at once in some viewer, especially if the action has an enablementExpression since this guy will iterate over every single element in the selection and will performs the enablement tests -sometime through an IActionFilter::testAttribute(...) on each and every one of them. This unnecessary processing makes a simple act of clicking on an element in a tree viewer quite costly although it doesn't have to be. Perhaps all these action can short-cicuit the enebalement calculations if they cannot be invoked at all (i.e., no context-menu or pulldown menu is about to show and they are not visible in the action bar of the viewer ...etc.)
Don't know if [Workbench] is the correct component area for this. Sounds like a good fit for Duoung too.
Popup menu object contributions do not listen to selection changes. It is only contributions that appear in the main menu, toolbars or views that listen to selection changes. They need to update their enablement even if they are not visible since they may have keybindings associated with them. Given that there can be a large number of these, it would still be worthwhiel to investigate possible performance improvements. For starters, we should verify that a failed expression or action filter test halts processing on the entire selection (i.e. a single failed element measn that the contribution is not applicable).
Assigning to component owner PW
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
