This question is locked. New answers and comments are not allowed.
Is it just me or is support for INotifyCollectionChanged in the RadSlideView only implemented rudimentary at best?
From what I'm seeing here the control will basically reset for every CollectionChanged event, regardless of the change action.
For example. If you have an appbar button the allows you to delete the items that's currently shown in the RadSlideView from the underlying collection, I would expect a well behaved control to move to the next item instead of going to the first item like it is currently implemented.
And yes I've verified that my underlying collection sends a CollectionChanged event with Action = Remove. And ONLY that one.
Any help would be appreciated.
From what I'm seeing here the control will basically reset for every CollectionChanged event, regardless of the change action.
For example. If you have an appbar button the allows you to delete the items that's currently shown in the RadSlideView from the underlying collection, I would expect a well behaved control to move to the next item instead of going to the first item like it is currently implemented.
And yes I've verified that my underlying collection sends a CollectionChanged event with Action = Remove. And ONLY that one.
Any help would be appreciated.
3 Answers, 1 is accepted
0
Hello Oliver,
Thanks for writing.
Indeed, RadSlideView does not optimally handle the collection changes. This is because we initially planned the control to be used to display static collections.
Since as of now it already supports the Pull-to-Refresh experience and there is demand for more complicated data scenarios, it is on our plans to upgrade it accordingly. In our latest Q2 2013 SP1 release we introduced a new and improved UI virtualization mechanism. We will put your requirement on our TODO list and will make sure to optimize the mechanism that handles source collection changes as well.
Is it alright for you to workaround this behavior by explicitly setting the SelectedItem to the desired one after modifying the source collection?
Please excuse us for any inconvenience caused.
Regards,
Deyan
Telerik
Thanks for writing.
Indeed, RadSlideView does not optimally handle the collection changes. This is because we initially planned the control to be used to display static collections.
Since as of now it already supports the Pull-to-Refresh experience and there is demand for more complicated data scenarios, it is on our plans to upgrade it accordingly. In our latest Q2 2013 SP1 release we introduced a new and improved UI virtualization mechanism. We will put your requirement on our TODO list and will make sure to optimize the mechanism that handles source collection changes as well.
Is it alright for you to workaround this behavior by explicitly setting the SelectedItem to the desired one after modifying the source collection?
Please excuse us for any inconvenience caused.
Regards,
Deyan
Telerik
Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
0
Oliver
Top achievements
Rank 1
Rank 1
answered on 23 Jul 2013, 12:21 PM
Since I don't have a choice the answer is yet.
The question is what's the best moment to "restore" the chosen next item after the SlideView has reset in response to the collection change. And if this will be noticable by the user.
The question is what's the best moment to "restore" the chosen next item after the SlideView has reset in response to the collection change. And if this will be noticable by the user.
0
Hi Oliver,
Can you please try setting the SelectedItem right after you modify your source collection?
Regards,
Deyan
Telerik
Can you please try setting the SelectedItem right after you modify your source collection?
Regards,
Deyan
Telerik
Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.