• 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: Threading, save panels, and segfaults
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Threading, save panels, and segfaults


  • Subject: Re: Threading, save panels, and segfaults
  • From: Andreas Monitzer <email@hidden>
  • Date: Sun, 11 Nov 2001 00:08:04 +0100

On Saturday, November 10, 2001, at 11:48 , R. Tony Goold wrote:

Your GUI interactions should be done from the main thread. If a secondary thread needs to make AppKit calls, it should notify the main thread (read up on Distributed Objects and Notification Centers) and let the main thread do it instead.

Notifications aren't thread safe, either :)
There are two ways: DO and sending events (the second one is pretty clumsy and should only be used when there is a single event that could happen, it usually requires an NSApplication subclass).

andy


  • Follow-Ups:
    • Re: Threading, save panels, and segfaults
      • From: "R. Tony Goold" <email@hidden>
References: 
 >Re: Threading, save panels, and segfaults (From: "R. Tony Goold" <email@hidden>)

  • Prev by Date: Re: Threading, save panels, and segfaults
  • Next by Date: Re: Controlling selection in NSTextFields
  • Previous by thread: Re: Threading, save panels, and segfaults
  • Next by thread: Re: Threading, save panels, and segfaults
  • Index(es):
    • Date
    • Thread