setFrame blocks thread?
setFrame blocks thread?
- Subject: setFrame blocks thread?
- From: Theo Vosse <email@hidden>
- Date: Thu, 20 Oct 2005 14:51:15 +0200
Hi,
I have two threads that both do something with the same view. I've
got an NSLock to keep them from working on the same data at the same
time, but it gets into a deadlock. The problem seems to be when one
thread (the "computing" thread) has gotten the lock, then the other
thread (the drawing thread) waits for the lock, and then the
computing thread calls setFrame. The debugger shows that that call
gets stuck in semaphore_wait. It seems that semaphore has to be
released by the drawing thread, but I don't control it. It looks as
if it's Cocoa internal. Did I see that correctly? Any suggestions?
Theo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden