Why not use the production of a frame from your secondary thread to drive calling -setNeedsDisplay on your view? Then you don't need to block any thread (and you really really do not want to block the main thread anyway).
On May 6, 2011, at 1:10 PM, eveningnick eveningnick wrote: > I need to wait, while the image is drawn (drawRect method is actually > called by the framework) from a different thread that supplies frames. > I am drawing images just to see that the output is correct, in the > final application i don't need them to be drawn on the screen but > saved into a file > > 2011/5/6 Graham Cox <graham....@bigpond.com>: >> >> On 05/05/2011, at 11:51 PM, eveningnick eveningnick wrote: >> >>> What i need - is to stop the thread A immediately after the thread B >>> has been spawned by a thread A. >> >> Hang on. Why use a thread at all? If Thread A simply calls the process B >> synchronously, it will achieve exactly what you have stated you want - that >> A will stop when B starts, and will continue when B finishes. >> >> --Graham >> >> >> > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/david.duncan%40apple.com > > This email sent to david.dun...@apple.com -- David Duncan _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
