At 3:13 PM -0800 2/16/06, Mars Saxman wrote:
So, this is interesting. I guess I have two questions. Since I'm
not running any threads, what constitutes a background task exactly?
Sockets, the UserCancelled function, debugger break (via Control-C),
and the busy cursor are all background tasks. I also see a few
things related to printing, temporary files, and window closing,
though I'm not sure under what circumstances those are invoked.
But, to be clear, sockets have code that prevents them from entering
events if an event is already in process -- except for the Error
event, which will go ahead and fire even if you're already in an
event.
That's why you only see this issue with Error, and why disabling
background tasks makes it go away.
Best,
- Joe
--
Joseph J. Strout
[EMAIL PROTECTED]
_______________________________________________
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>
