Please add ability to bind IsRefreshing to ListView?

4 posts, 1 answers
  1. Erik
    Erik avatar
    52 posts
    Member since:
    Jan 2011

    Posted 21 Oct 2015 Link to this post

    Hi -

    I have a list view that has "pull to refresh" enabled, and it works great -- refreshes and shows a spinner while it's refreshing.

     There are other situations that cause me to refresh the data, though, and in a ViewModel, and I'd like to have a property that I can update in the view model that could be bound to the "IsRefreshing" so that I can see the same refresh spinner when I am programmatically refreshing the data in the list view.

    I can use an a Xamarin "ActivityIndicator" to show a spinner, but then when we "pull to refresh" we see BOTH spinners, and it looks bad.  This approach works fine for the programmatic-only refresh, but the pull becomes bad.  If I remove the activity indicator, then I don't see anything when the programmatic refresh happens.

     I see two options: Make it possible for me to set the "IsRefreshing" state for the ListView based on binding, or allow me to suppress the RadListView spinner in favor of the activity indicator - which would be seen then in both programmatic and pulls as the only indicator.

    Let me know if I'm missing something or if this is possible.

    I really appreciate the help and support.

    Cheers -




  2. Answer
    Pavel R. Pavlov
    Pavel R. Pavlov avatar
    1251 posts

    Posted 26 Oct 2015 Link to this post

    Hello Erik,

    I understand your requirement. However, I am not sure that this is the best approach possible. I would like to turn your attention to the fact that the "pull to refresh'' is a UI interaction. This means that it should not be triggered from code. It is designed to allow the end user to easily force refresh on the list with a gesture. The question that you need to answer is: Do you really need to notify the end user that a refresh is in process? Another good question is: Do you need to use the same ActivityIndicator for that notification?

    My point is that even if you need to notify the end user that there is a refresh in process it would be better to use separate ActivityIndicator. It you force the RadListView to visualize its builtin indicator, the items that are currently loaded will jump. My opinion is that this is not a good user experience and if I were you I would go with different approach.

    I can make more clear suggestion but I need more details about your specific scenario. If you shed some light about your application, the user experience that you are after and the context of the app I would be able to give you at least a different view on the construction of the UI components and their features.

    I hope this information is helpful. Please do not hesitate to contact us again if you have additional questions.

    Pavel R. Pavlov
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. Erik
    Erik avatar
    52 posts
    Member since:
    Jan 2011

    Posted 28 Oct 2015 in reply to Pavel R. Pavlov Link to this post

    Thanks for the response.  I think we've figured out an answer on our side which gets us where we need to be.  Your thoughts make sense, and if I have any additional questions, I'll raise them.
  4. Gerry
    Gerry avatar
    34 posts
    Member since:
    Jan 2017

    Posted 15 Feb 2017 in reply to Pavel R. Pavlov Link to this post

    Whether the program is updating the list automatically, or the user via a pull gesture, it seems to me using the same Activity Indicator is less confusing to the user than using two different ones. When the same (style of indicator is used) the user then understands what is happening (in the background) is the same.
Back to Top