It still doesn't work - And even if it did, I wouldn't recommend it as
it's not intention revealing, and (IMO) would rely to much on the
particular implementation of "-
performSelectorOnMainThread:withObject:waitUntilDone:".
If you're already on the main thread, I think that this call:
...should *conceptually* be viewed as the same as this call:
[obj foo];
If, like in this case, you want to do something after the current run
loop, and on the same thread, you should use a regular "-
performSelector:withObject:afterDelay:".
j o a r
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
