Unless you do App.DoEvents within one, events are blocking. Which means it shouldn't matter where you run in, the window initialization is stopped while the code is executing.
On 12/8/06, Fargo Holiday <[EMAIL PROTECTED]> wrote:
Speaking of that, I'm curious if you're having your RB app do this in the open event, or triggered via button. The button method strikes me as a much more accurate test of the actual string processing, since you've already waited through rendering the window, loading the other pieces of framework inside that 3MB block, and whatnot, but that's just me.
_______________________________________________ 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>
