site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com However all my 'real' work in the cocoa app, including the call in question, is already done in a background thread, so I get the impression I'm safe to use the same runloop construct within the library. I'm about to try it anyway... On May 9, 2008, at 3:42 AM, Andy Green wrote: That was exactly my concern: I don't mind pauses in a console app, but I didn't want to tie up the gui. My library does 'things' with disks, I need to perform the DAUnmount/eject right in the middle, and I just wanted the same library call to work whether called from console or GUI. Is your background thread already calling CFRunLoopRun or is just running to completion? My personal preference is to have all the DA callbacks on an thread that's handling it's own events- either in their own thread, or attached to the main thread (in a GUI App). If your having to structure your code to call RunLoopRun just so you can let your callbacks fire it's been my experience that I'm working to hard and need to rethink what I'm doing. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com