• 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
DO vs NSLock with threads and AppKit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

DO vs NSLock with threads and AppKit


  • Subject: DO vs NSLock with threads and AppKit
  • From: Christian Mike <email@hidden>
  • Date: Mon, 23 Jul 2001 08:12:46 -0500

I understand that the AppKit is not thread safe. I am a little confused,
however, about when you can use an NSLock to make it thread safe versus when
you must use DO.

For instance, if I am simply sending a setStringValue to an NSTextField,
should I use DO, or will an NSLock be good enough?

Are there cases when an NSLock would not work as opposed to DO?

Thanks.

Michael Christian
Thomson multimedia Inc.


  • Prev by Date: Re: Goofy NSDrawer behavior
  • Next by Date: Re: DO vs NSLock with threads and AppKit
  • Previous by thread: Sometimes, the smallest snippets of code..
  • Next by thread: Re: DO vs NSLock with threads and AppKit
  • Index(es):
    • Date
    • Thread