• 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: GUI not responding possibly because of NSRunLoop, what can I do?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUI not responding possibly because of NSRunLoop, what can I do?


  • Subject: Re: GUI not responding possibly because of NSRunLoop, what can I do?
  • From: "Devraj Mukherjee" <email@hidden>
  • Date: Wed, 8 Aug 2007 09:26:05 +1000

Hi Alastair,

Thanks again for your response. I have managed to get over the use of
NSRunLoop. I can use NSApplicationMain without passing it a default
NIB name and it does exactly what I need to.

Thanks again for your time.

On 8/7/07, Alastair Houghton <email@hidden> wrote:
> On 7 Aug 2007, at 12:21, Devraj Mukherjee wrote:
>
> > Hi Alastair,
> >
> > Thanks for taking time to assist me. I have implemented the
> > NetSocket's delegate methods to do what is required. My application
> > doesn't have a default GUI launched. It waits and listens to events on
> > the socket and launches GUI elements. So for a lot of its life its
> > headless.
> >
> > Can I achieve this by working with something like NSApplication?
>
> I'm not sure what your question means exactly.  Are you asking
> whether your app should be a GUI app or not?
>
> It sounds like you might be trying to implement the kind of
> application you often see in the status area (the right hand side of
> the menu bar).  In that case, firstly you might want an NSStatusItem
> so that users can easily control your application, and secondly you
> should find that you can display windows easily enough using standard
> Cocoa techniques (i.e. loading them from a nib file if necessary,
> then sending them -makeKeyAndOrderFront: messages).
>
> In such a case, you'd probably want to use LSUIElement in your
> Info.plist (see, e.g. <http://www.cocoadev.com/index.pl?LSUIElement>
> for more information on that).
>
> Kind regards,
>
> Alastair.
>
> p.s. Please copy the list on your responses.  That way when someone
> else searches the archives for answers to a similar question, they'll
> find this thread.
>
> --
> http://alastairs-place.net
>
>
>


--
"I never look back darling, it distracts from the now", Edna Mode (The
Incredibles)
_______________________________________________

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

References: 
 >GUI not responding possibly because of NSRunLoop, what can I do? (From: "Devraj Mukherjee" <email@hidden>)
 >Re: GUI not responding possibly because of NSRunLoop, what can I do? (From: Alastair Houghton <email@hidden>)
 >Re: GUI not responding possibly because of NSRunLoop, what can I do? (From: Alastair Houghton <email@hidden>)
 >Re: GUI not responding possibly because of NSRunLoop, what can I do? (From: Alastair Houghton <email@hidden>)

  • Prev by Date: Re: Cocoa callback handling
  • Next by Date: Cocoa and messages to nil, revisited
  • Previous by thread: Re: GUI not responding possibly because of NSRunLoop, what can I do?
  • Next by thread: Caching issues with NSOpenPanel
  • Index(es):
    • Date
    • Thread