FROM : Chris Kane
DATE : Thu Jan 02 20:34:41 2003
On Wednesday, January 1, 2003, at 09:26 PM, David Rio Vierra wrote:
> Before detaching your thread, store your main thread's current run
> loop in an instance variable. Then you can just create your timer
> with the +timerWith... methods instead of the +scheduledTimer...
> methods, and add it to that runloop yourself from your second thread.
Since NSRunLoops are not thread-safe, it is not a good idea to play
with one from another thread.
Chris Kane
Cocoa Frameworks, Apple
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Thu Jan 02 20:34:41 2003
On Wednesday, January 1, 2003, at 09:26 PM, David Rio Vierra wrote:
> Before detaching your thread, store your main thread's current run
> loop in an instance variable. Then you can just create your timer
> with the +timerWith... methods instead of the +scheduledTimer...
> methods, and add it to that runloop yourself from your second thread.
Since NSRunLoops are not thread-safe, it is not a good idea to play
with one from another thread.
Chris Kane
Cocoa Frameworks, Apple
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| Related mails | Author | Date |
|---|---|---|
| Ted Lowery | Jan 2, 06:05 | |
| David Rio Vierra | Jan 2, 06:26 | |
| Chris Kane | Jan 2, 20:34 |






Cocoa mail archive

