I am just off to try writing code that does the fgetln() in a new
thread and then calls
performSelectorOnMainThread:withObject:waitUntilDone:NO to
communicate the results, which I think might work.
It worked. I had to create and add an empty port to my run loop to
stop the run method exiting immediately... perhaps there is a better
way to handle this?
"Note: Regardless of the date you specify in runMode:beforeDate: and
runUntilDate:, a run loop with nothing to do (that is no sources from
which to receive input) exits immediately. You must add the input
sources to the run loop mode before you start the run loop. Other parts
of the system may add their own sources to a particular run loop mode,
but do not depend on this always being the case. Add an empty NSPort to
a run loop if you need to guarantee that it does not exit immediately"
I'd forgotten about empty run loops; they exit immediately.
Rob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Rendezvous-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
