On Oct 14, 2012, at 4:34 PM, Kyle Sluder <k...@ksluder.com> wrote: > Okay, at this point you need to step back a bit and actually work > through your threading architecture. The first question to ask yourself > is whether you actually understand multithreading. The second question > to ask is whether you actually understand how your code is using it.
Point well taken :) Just to clarify, my understanding is that when you want to update the UI from code that is not on the main thread, you will need to use performSelectorOnMainThread. Therefore I created the updateStatus: method to ensure the status field is always updated on the main thread, no matter from which thread it is being called. But in my naivety, I probably overlooked something very basic. > That might mean breaking out the whiteboard, drawing a timeline, and > going through your code with a fine-toothed comb to mark down every > possible context switch. I will do certainly that. - Koen. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
