• 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: call scrollRangeToVisible in multi-threads cause application dead lock
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: call scrollRangeToVisible in multi-threads cause application dead lock


  • Subject: Re: call scrollRangeToVisible in multi-threads cause application dead lock
  • From: Erik Buck <email@hidden>
  • Date: Wed, 7 Mar 2007 07:45:40 -0800 (PST)

Apple states that the AppKit is generally NOT thread safe.  Why on earth would you think that having critical section in YOUR code would magically make the AppKit thread safe.  Until or unless Apple makes the AppKit thread safe, you are out of luck and there is no way you can correctly call AppKit methods directly from multiple-threads.

  Consider using -performSelectorOnMainThread:withObject:waitUntilDone:modes:  from within your multiple-threads so that the AppKit method is always executed by the main thread.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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: call scrollRangeToVisible in multi-threads cause application dead lock
      • From: David Gish <email@hidden>
  • Prev by Date: Re: Multi-threaded help
  • Next by Date: Re: Multi-threaded help
  • Previous by thread: Re: call scrollRangeToVisible in multi-threads cause application dead lock
  • Next by thread: Re: call scrollRangeToVisible in multi-threads cause application dead lock
  • Index(es):
    • Date
    • Thread