If all you actually want is a flag, why not just have a flag? When the other
thread gets around to examining the flag, it can do what it wants.
If you need to synchronize access to the flag, because say, the number of times
they press the button is significant, then put an @synchronized directiv
On Oct 8, 2008, at 7:46 PM, John Zorko wrote:
Hello, all ...
If a certain flag is set, my app needs to advance to the next item
in a list to process it when the previous item is done. However, I
want the user to still be able to stop it, so I don't want to hang
the UI. In effect, if th
It sounds like you want an NSOperationQueue, which would map to your
problem on a high level.
http://developer.apple.com/documentation/Cocoa/Reference/NSOperationQueue_class/Reference/Reference.html
I don't know Win32, but PostMessage() sounds a lot like
NSNotificationCenter's postNotificati
