FROM : j o a r
DATE : Fri Apr 15 19:50:42 2005
On 15 apr 2005, at 00.33, Joshua D. Orr wrote:
> I am guessing you are using a NSTimer. Your new thread probably
> does not have
> a message run loop running, and NSTimer makes use of that.
Please check with the documentation. From NSRunLoop API docs:
"In general, your application does not need to either create or
explicitly manage NSRunLoop objects. Each NSThread, including the
application’s main thread, has an NSRunLoop object automatically
created for it. If you need to access the current thread’s default
run loop, you do so with the class method currentRunLoop."
This thread has been pretty weird all along. I'll write a follow up
message later with some ideas that you might try if you want to get
this working. But first I need to watch a movie with the wife.
j o a r
DATE : Fri Apr 15 19:50:42 2005
On 15 apr 2005, at 00.33, Joshua D. Orr wrote:
> I am guessing you are using a NSTimer. Your new thread probably
> does not have
> a message run loop running, and NSTimer makes use of that.
Please check with the documentation. From NSRunLoop API docs:
"In general, your application does not need to either create or
explicitly manage NSRunLoop objects. Each NSThread, including the
application’s main thread, has an NSRunLoop object automatically
created for it. If you need to access the current thread’s default
run loop, you do so with the class method currentRunLoop."
This thread has been pretty weird all along. I'll write a follow up
message later with some ideas that you might try if you want to get
this working. But first I need to watch a movie with the wife.
j o a r
| Related mails | Author | Date |
|---|---|---|
| Dan Yocom | Apr 14, 23:41 | |
| Joshua D. Orr | Apr 15, 00:33 | |
| Dan Yocom | Apr 15, 16:26 | |
| Lindsey Spratt | Apr 15, 17:35 | |
| Joshua Orr | Apr 15, 18:55 | |
| j o a r | Apr 15, 19:50 | |
| j o a r | Apr 15, 21:20 |






Cocoa mail archive

