yep, loop ends yield to the main loop, and the DisableBackgroundTasks
pragma is the proper solution.
mike
--
Mike Woodworth
[EMAIL PROTECTED]
On Feb 16, 2006, at 4:39 PM, jon pipitone wrote:
Hey all,
An interesting result:
That is, a DataAvailable event called on a socket subclass. This
method calls my custom logger's debug method. In that debug
method I loop through listeners to report this error. It is
exactly on the first line of the for loop in the Logger.Debug()
method which is highlighted in the debugger. That line reads:
for i = 0 to ubound( listeners )
Then the TCPSocketSubclass.Error event appears on the stack
entirely interrupting the sequence of events.
The only thing I can see occurring here is some sort of compiler
optimization in the for loop that calls the equivalent of
App.DoEvents... is that possible?
If I put a #pragma DisableBackgroundTasks True before the loop in
my logger I no longer get this behaviour. So maybe this confirms
my suspicion?
jp
_______________________________________________
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>
_______________________________________________
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>
