On Oct 05, 2006, at 16:34 UTC, Stephen Dodd wrote: > The docs say only "Similar to Refresh but causes the control to be > redrawn a some point in the future." > > When is it appropriate to use this?
Whenever the content of a control has changed in a way that the RB framework might not know about (most likely, it's a canvas control whose content you draw yourself), and you don't need the change to be drawn immediately -- i.e., it's not an animation . > What are the probabilities that > a user would see old content while waiting for "the future'? Slim to none, unless you've stuck the main thread into some lengthy processing loop. Invalidation is the standard way that controls update; it marks the control to be redrawn, but then all the invalidated controls are redrawn at once each time through the main event loop. > Is it approriate to call mycontrol.invalidate repeatedly in a loop assuming > that only one update will take place at the end? Yes -- not that I know anything about the internal implementation, but that's what the standard meaning of "invalidate" implies. HTH, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ 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>
