Busy indicator of RadPDFViewer while loading documents

3 posts, 1 answers
  1. Florian
    Florian avatar
    10 posts
    Member since:
    Apr 2011

    Posted 15 Aug 2013 Link to this post

    Hello,

     

    We are using RadPDFViewer in Silverlight application. We have a list of documents to be loaded dynamically in RadPDFViewer. The scenario is, If we select one document from the list then it should be loaded and displayed in the RadPDFViewer. The loading and display of all the documents works absolutely fine however there is small problem with loading (busy) indicator of the RadPDFViewer. For some documents, RadPDFViewer does not show the loading (busy) indicator even though it takes some time for it to load the document.

     

    Our ideal situation would be, when we select any document then RadPDFViewer should show the busy indicator while loading the document and then display it.

     

    Thanks,
    Florian

  2. Answer
    Petya
    Admin
    Petya avatar
    975 posts

    Posted 20 Aug 2013 Link to this post

    Hi Florian,

    Generally, the busy indicator is shown between the moment the DocumentSource of RadPdfViewer is changed and the moment the DocumentSource is loaded. That said the delay in your application is most likely caused by something else, for example the rendering of the elements once the document is loaded.

    In case you think something else might be causing the issue please open a support ticket and provide a sample project along with one of the files you experience the issue with. 

    Regards,
    Petya
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for SILVERLIGHT.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  3. DevCraft banner
  4. Florian
    Florian avatar
    10 posts
    Member since:
    Apr 2011

    Posted 23 Aug 2013 Link to this post

    Thank you for your reply.

    It looks like the problem was caused by an internal error. Is is gone using the current nightly build hotfix.

    Have a nive day,
    Florian
Back to Top