On Mar 30, 2006, at 10:41 AM, Dennis Birch wrote:
Finally I came
up with the workaround of instantiating a timer that adds a brief
delay, and
that did succeed. But it really seems like a hack. I don't
understand what's
going on, or how I could better code around this. Any ideas?
Ah, looking at the code closer, Spotlight would be indexing the new
copy, not the original and so that shouldn't be stopping you. But,
along these same lines I have found times when the Finder seems to be
a little slow releasing everything, especially in some tight code
such as this forcing one to come up with the need to delay execution.
A couple of my programs work great 99% of the time without the delay
but on occasion I will hit return codes that indicate the file is not
available when it should be. Like you, I never see this when stepping
through the debugger since there is sufficient delay. It's a pain but
I don't think RB is the cause of the problem here.
=== A Mac addict in Tennessee ===
_______________________________________________
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>
|