On 2009 Sep 11, at 05:55, John Chang wrote:
Just to update you guys. We managed to reproduce the problem in-
house and
catch it in the debugger.
I'd be interested to know how John is going to fix this problem. I
myself have used the performSelector:withObject:afterDelay:0.0
solution in situations like this, usually with good results, but it
always feels like a kludge, and I worry -- what if someday I also
accidentally delay the code that's supposed to run first, to solve a
different problem. So I've just moved the problem from crashNow to
crashAfterDelay:. Sometimes I feel better if I make the delay .01 or
so.
The ideal solution is to look around for another method that's somehow
guaranteed to run later. That's ideal, but you can't always find one.
_______________________________________________
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
