This change will allow us to handle having the same items multiple times in the list, for example ?\226?\128?\156Ryan Frishberg?\226?\128?\157 can now be in the list twice.
In order to do it, rather than using the item to find the itemRenderer or to tell the list that an item?\226?\128?\153s been selected, we need to use the index instead. Methods like getItemRenderer and getRendererItem were changed to accept an index rather than an item. Other methods were added, like isItemIndexSelected() because I felt isItemSelected() is still a useful method to have, even though it?\226?\128?\153s ambiguous when multiple items come in to play.
For now, I just tried to change the parameters where needed. Some of the names of the methods were updated to reflect the change, but others weren?\226?\128?\153t because PARB is going to review a lot of this on Thursday, so it?\226?\128?\153s easier to make a name change only once (and after PARB approves it).
I also added properties to ItemExistanceChangeEvent.as. In a later checkin, I?\226?\128?\153ll create a separate RendererExistanceChangeEvent.as for DataGroups and use ItemExistanceChangeEvents only for IVisualElementContainers (Halo containers will also dispatch these events). However, this needs to be PARB reviewed, so I figured it?\226?\128?\153s best to hold off on this change until later.
Also included in this checkin are some small ASDoc updates to no longer use any of the ?\226?\128?\156addItem(), numItems?\226?\128?\157, and instead use addElement() or numElements where appropriate.
QE Notes: Steve's excluded any failing tests. As noted in the checkin, there will probably be some renaming related to these methods. Also, add some tests for duplicate items now.
Doc Notes: None
tests: checkintests, mustella DataGroup, FxDataContainer, FxList