Initial BusyIndicator Start

Thread is closed for posting
3 posts, 0 answers
  1. Jon
    Jon avatar
    4 posts
    Member since:
    Apr 2012

    Posted 19 Jun 2012 Link to this post


    I have an app that has two pages in it. The Second page can take a few seconds to load due to the large number of objects on the page an the data I'm loading from XML so I thought that it would be good to put a BusyIndicator while this loaded. The problem is that when I'm on page 1 (login) and I basically say "Start" it navigates to Page 2 and starts the load, but the UI doesn't actually update and show the busy indicator until Page 2 is completed loaded so the app just sits on page 1 doing nothing for a few seconds.

    I've tried starting the Progress bar before Page 2 components load but it doesn't help. Anyone run into this issue? Any advice?
  2. Victor
    Victor avatar
    1358 posts

    Posted 20 Jun 2012 Link to this post

    Hi Jon,

    Thank you for the question.
    In your case, you need to redesign your pages so that they don't take so long to load. There is no other way because the XAML loading happens on the UI thread. RadBusyIndicator is also on the UI thread and starting it will have no effect since the thread is busy doing other stuff (loading page content). RadBusyIndicator is appropriate when performing a long running operation like downloading a file from the web or running some algorithm that does real work (calculating subatomic particle collisions for example :) ).

    Please write again if you have other questions.

    All the best,
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

  3. Eugeniy
    Eugeniy avatar
    63 posts
    Member since:
    Feb 2011

    Posted 25 Jul 2012 Link to this post

    Try to call navigating and loading inside Disptacher.BeginInvoke, after setting busyindicator.isrunning = true, it may help.
    Since animation started it is handled by GPU thread, so blocking UI thread will not block BusyIndicator animation.

    But you should better use background thread to load large amount of data from your xml.

Back to Top