Re: Diskarbitration callback
Re: Diskarbitration callback
- Subject: Re: Diskarbitration callback
- From: Kevin Elliott <email@hidden>
- Date: Fri, 9 May 2008 10:26:46 -0700
On May 9, 2008, at 5:44 AM, Axel Luttgens wrote:
Le 9 mai 08 à 12:42, Andy Green a écrit :
Hi Kevin,
Thanks for your comments; a couple of responses inline below
[...]
That was exactly my concern: I don't mind pauses in a console app,
but I
didn't want to tie up the gui.
That's one of the reasons that led me to suggest
CFRunLoopRunInMode(); in fact, as it has been used, the call to
CFRunLoopStop() could even be removed from AndygDiskArbCallback().
(unless, of course, I'm terribly wrong; as I already noticed, I'm
not a guru...)
Ahh... Not sure what your goal was, but CFRunLoopRunInMode basically
means "Only process events that are in the following set (mode)".
Everything else will be queued, which could obviously cause hickups,
etc. Now, of course, if your already in your own thread it's a non-
issue. The main thread has it's own runloop which will happily
continue on it's own.
Generally speaking, I don't think CFRunLoopRunInMode is something for
"normal" use. It's primary purpose is for things like creating old
fashioned modal dialogs and the like. If your calling it directly you
are either doing something sneaky and clever, or your using it wrong.
One of those is a lot more common than the other ;-) _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden