What about performSelector:withObject:afterDelay: with a delay of 0.0, I
believe, will perform the selector after the current iteration of the run loop.
Not sure about thread safety, though.
On Oct 13, 2011, at 10:17 PM, Steve Steinitz wrote:
> Hi Richard,
>
> The advice you've received already is more sound than what I'm about to tell
> you. But my crude technique has solved the problem you mention and similar
> problems.
>
> I wrote the following class method on a utility class into which I throw
> stuff:
>
> + (void)
> waitUntilEndOfNextRunLoop
> {
> [[NSRunLoop mainRunLoop] runUntilDate:[NSDate distantPast]]; // finish
> current iteration
> [[NSRunLoop mainRunLoop] runUntilDate:[NSDate distantPast]]; // once
> more so selection updates
> }
>
> Whenever I have a problem like the one you mention, I invoke that method and
> all is well. I confess, I invoke it right and left. I has no effect on
> performance that I can notice. But its far from pretty.
>
> Cheers,
>
> Steve
>
> _______________________________________________
>
> Cocoa-dev mailing list ([email protected])
>
> 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/wsquires%40satx.rr.com
>
> This email sent to [email protected]
_______________________________________________
Cocoa-dev mailing list ([email protected])
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 [email protected]
