WorkingSetView does not yet include WorkingSetSort module, so it's best to continue to use the event so there's no new dependency introduced.

Sorry, I missed that other case where event is handled. It's more efficient to insert an item into a sorted list in the sorted position (as opposed to appending to end and re-sorting entire list), but we'll still need this code anyway when someone sorts via context menu, and the length of the list is short, so it's probably not worth refactoring that code.

Since this event has 2 different uses, it needs to be documented here:
1. notifies working set view to sort list
2. disable automatic sorting when working set manually re-sorted via drag/drop

Also, document how you make sure the correct event gets handled in the correct situation. I'm noticing that WorkingSetView handles the event even after drag/drop, so I'm not sure how that all works. Hmmm. I'm remembering why I prefer the original design of having 2 separate events. :)

The main problem with that design was that the event names were not as clear as they could have been. What do you think about having 2 events: `workingSetSort` and `workingSetDisableAutoSorting` ? You've definitely made some other improvements here -- I'm not suggesting that you throw those out.