I'm sorry if this keeps coming up time after time, but this must be the craziest part of using RB. Something as simple as a ProgressBar that's just much more pain to use than it should be.
Calming down now.... Yes, I searched the archives, but couldn't find a complete answer. 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? 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) So there seems to be some voodoo wisdom in putting the update in a thread (this is where it gets WAY too complicated for a simple progressbar), but again, I couldn't find a complete example anywhere in the archives. Sorry if I missed it, but I did look. So I ask... Why is something that's seemingly SO simple, so hard to deal with? Why doesn't it just work? And, if there is a reasonable explanation for it (which I'd love to hear), and a reasonable workaround (which I'd REALLY love to hear), why isn't it in the help? I mean, not even the performance challenged .update tip is in the help. Can some helpful soul point me in the right direction? Sorry about the (not really) ranting... :) Thanks, Ray _______________________________________________ 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>
