On 4/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > On Apr 27, 2007, at 03:04 UTC, Peter K. Stys wrote: > > > > Very curious yes. Are you sure your button code is returning as > > soon > > > as it runs the thread? > > > > I imagine yes, 'cause this is the whole button: > > I agree. That's really weird then. The only way I can imagine this > could happen is if your thread calls some plugin that doesn't play > nicely. Plugins can tie up all threads if they don't yield properly. > A few other things can too -- an unusual declare, I would suppose, plus > maybe something like FolderItem.CopyFileTo. What's your thread doing? > > A good way to track this down, if you don't see any likely suspects, > would be to run Shark on it (if you have a Mac) while it's stuck. > > If you can't figure it out, I'd be happy to take a look at it (pro > bono), because I'm very curious myself. >
I can send you the thread code, but the point is, the thread gives a beach ball for 10-20 sec, then the app is released and the remaining batch runs in the background as expected; the same code never beach-balled my app while in a button (tho the main thread was hung up for the duration of the batch however). Go figure. P. -- ------------------------------------------------------------------------------- Peter K. Stys, MD Professor of Medicine(Neurology), Senior Scientist Ottawa Health Research Institute, Div. of Neuroscience Ottawa Hospital / University of Ottawa Ontario, CANADA tel: (613)761-5444 fax: (613)761-5330 http://www.ohri.ca/profiles/stys.asp ------------------------------------------------------------------------------- _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
