Sounds like a focus issue. If the list view is regaining focus, maybe
we shouldn't attempt to reset the selection.
On Aug 22, 2009, at 2:53 PM, Todd Volkert wrote:
I'm running into an issue in my Pivot app and wanted to see if it's
a pivot
issue or an app issue:
I have a list view that is in single select mode. If I click on
some other
part of the app, it loses focus. Then I click back on the *selected
item*
of the list view, and it fires a selectedRangesChanged event. In my
app,
when I receive this event, I query the server for back-end data and
block
user input until the server responds. This yields a poor user
experience
when the user clicked on the item that was already selected.
So should ListView check to see if the selected ranges *really*
changed, or
should I perform that check in the app by looking at the
previousSelectedRanges argument?
Thoughts?
-T
