![]() This will pause your work for a specified time duration and allow other things to kick in and update. The hackiest solution of all is to use app.doevents after calling progressbar.refresh. ![]() Use a helper application, the most complex solution, but you’ll get the best the performance and a smooth updating interface. Use a thread, like others have suggested, so that the window can be updated while the thread is running. ![]() You must use Refresh here as invalidate is coalesced and won’t update until your task has finished. Use a short delay timer to do your work, so that there’s a gap between the action being selected and the task starting, giving Window services a few milliseconds to make the progressbar visible. You can fix this with a bunch of solutions. Long and the short of your problem is that Window services haven’t yet had time to make the progressbar visible, so any calls to updating it are just wasting cycles.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |