I want to update a progessbar in a tight loop. And of course, it doesn't update for God knows what reason. You have to put in a progressbar.update. Why? Why should this simple control need extra care?
It doesn't. It works the same as all other controls. Have you tried putting the code to do the loop in a thread? But of course, if I do put in a .update in my loop, the performance of my loop (which is just drawing a bunch of characters to a canvas) degrades TREMENDOUSLY. WHY? I mean, all it has to do is draw a small rectangle of pixels to the screen. Does it really have to degrade that much? (sorry for the lack of timing details...I couldn't believe it was so much slower and just went to bed) You have no idea how much code is required to "draw a small rectangle of pixels." It's mountains. As the other responder said, put in an extra counter and only update every 25th, 100th, 1000th, or whatever other number makes sense. Hint: if your progress bar is 200 pixels long, updating more often than MaxValue / 200 is wasting your time. Craig _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
