InfoPath form "busy" indicator - InfoPath Dev
in

InfoPath Dev

InfoPath form "busy" indicator

Last post 08-20-2009 11:12 AM by lfsaunders. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 08-17-2009 07:33 PM

    InfoPath form "busy" indicator

    I'm creating an InfoPath 2007 form (client, not browser) that connects with SharePoint lists. Sometimes the interactions with the lists are slow. What I'd like to do is create a visual indicator on the form that's it's "busy" processing the last request.

    I've got 2 images that I've placed in picture controls on the form, Busy and Not Busy. The busy image is hidden by default. When a button is clicked that starts some long running process, I'd like to hide the not busy image and display the busy image, When the code for the long running process completes, hide the busy image and display the not busy image.

    What I'd like to do is find a way to make the form refresh its display after the button click event that starts the long running process.

    Ideas?

    Larry
  • 08-18-2009 11:27 PM In reply to

    Re: InfoPath form "busy" indicator

    I think this is hard to do without writing some code. Rules to conditionally hide a section won't work because the view won't repaint until it comes back from the query (you might verify that, but that's my understanding). You need to write some code that shows your indicator and then goes off to query the list.

    Patrick Halstead
    Project Manager at Qdabra
  • 08-20-2009 11:12 AM In reply to

    Re: InfoPath form "busy" indicator

    The problem is exactly that the view doesn't repaint while the button event is being processed.

    I can't know to do anything until the user clicks the button requesting the processing. But any conditional formatting I activate (display the busy image) at the begining of the button event code just gets ignored because the view won't repaint until the button event processing is complete.

    Forcing a repaint inside the button click event after I set the conditional formating or breaking the calculation into two events (button event and separate event, raised by the button event, to do the list processing), either would give me what I need. Ideas?

    Larry
Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.