• 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: threads vs run-loops for keeping your GUI responsive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: threads vs run-loops for keeping your GUI responsive


  • Subject: Re: threads vs run-loops for keeping your GUI responsive
  • From: Pontus Ilbring <email@hidden>
  • Date: Fri, 9 Dec 2005 16:43:57 +0100

On 12/9/05, Niko Matsakis <email@hidden> wrote:
> It seems like what I really want to do is simply have a function
> which does a discrete amount of work: processing one line from the
> file, for example, and to repeatedly schedule calls of this function
> onto the run loop. This way, if no other events should occur, my
> function can get invoked, and I can do some work. Eventually, when
> the work is done, I can exit the modal session as usual.
> Transforming my code to work this way would be quite trivial.

Have you considered NSApplication's runModalSession:?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >threads vs run-loops for keeping your GUI responsive (From: Niko Matsakis <email@hidden>)

  • Prev by Date: searchkit 10.4 and chinese language word boundaries
  • Next by Date: Re: threads vs run-loops for keeping your GUI responsive
  • Previous by thread: threads vs run-loops for keeping your GUI responsive
  • Next by thread: Re: threads vs run-loops for keeping your GUI responsive
  • Index(es):
    • Date
    • Thread