Re: Confused about CFRunLoop
Re: Confused about CFRunLoop
- Subject: Re: Confused about CFRunLoop
- From: "Kyle Sluder" <email@hidden>
- Date: Tue, 18 Mar 2008 00:12:22 -0400
On Tue, Mar 18, 2008 at 12:01 AM, Brian Greenstone <email@hidden> wrote:
> Cocoa is really only necessary for GUI based apps
We seem to have not made any progress. Until you change that
misconception, this is going to be rather difficult. Back when this
OS was known as NEXTSTEP and Core Foundation didn't exist things
seemed to work just fine...
> Both block any user input, so there's no way to use menu's or controls
> in any windows. This has nothing to do with Cocoa vs. C or whatever
> since they both do the exact same thing.
You're right, which is why you should re-read what I said. You're
doing it wrong. It is a very, very rare thing to create your own run
loop. If you do, you better know what you're doing; in this case,
what you're doing is throwing yourself into a modal loop that prevents
AppKit from dispatching your events. If you read the docs, you will
see that run loops exit when all their input sources have been
detached. All your events come in from the Window Server on an input
source which is attached to your main run loop. *If you create your
own run loop these events will never be dequeued, as the main run loop
is waiting for yours to finish.*
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden