Description Adam Neal 2010-12-01 17:31:51 EST

Build Identifier: I20100608-0911

Selection events should not be sent to listeners when the down/up key is being held.  Rather it should wait until the key is release, and then send the selection notification about the last element.

Currently, when users try to navigate quickly in the tool, they find that they can't do things like holding the down key in the project explorer since view that listen for selection changes are getting bombarded with selection events and then take time to refresh.  This makes the tool lag, and when the user lets go, it seems like it doesn't response since its still processing all the selection events being sent, each one taking time to refresh all the listening views.

I believe it would be much more efficient if we simply did not send any selection events while the down/up arrow is still depressed.

Reproducible: Always

Steps to Reproduce:
1.put a lot of elements in your project explorer
2.ensure you have views open that react to selection changes
3.start at the top, and hold the down key to scroll through the entries.
- you will find that the selection in the PE will start looking choppy
4. hold for more then a second and then release
- you will find that it will keep going for a short while as it continues to process the events. 
- in our tool this is amplified as we have a few views which load a lot of data based on selected elements.