• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Asynchronous Notification Failed
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Asynchronous Notification Failed


  • Subject: Re: Asynchronous Notification Failed
  • From: Graham Cox <email@hidden>
  • Date: Tue, 17 May 2011 10:43:10 +1000

On 17/05/2011, at 7:19 AM, Bing Li wrote:

> I was told I should implement a RunLoop in
> the code. How to do that?


you call [NSApp run];


Which requires that you have initialised NSApplication, which a default Xcode Cocoa project does for you (and where the above method is also called for you). Look at the default main.m file.

To NOT have a run loop available takes much more work than to have one, so just let Xcode set up your project and it's ready to go. You don't need to know anything much about run loops to write Cocoa apps, but if you don't have it there, lots of stuff won't work.

--Graham


_______________________________________________

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

  • Follow-Ups:
    • Re: Asynchronous Notification Failed
      • From: Graham Cox <email@hidden>
References: 
 >Asynchronous Notification Failed (From: Bing Li <email@hidden>)

  • Prev by Date: Re: how to create a NSMenuItem without memory leaks
  • Next by Date: Re: Asynchronous Notification Failed
  • Previous by thread: Re: Asynchronous Notification Failed
  • Next by thread: Re: Asynchronous Notification Failed
  • Index(es):
    • Date
    • Thread