Re: Very strange problem about "setString" method of NSTextView.
Re: Very strange problem about "setString" method of NSTextView.
- Subject: Re: Very strange problem about "setString" method of NSTextView.
- From: j o a r <email@hidden>
- Date: Sun, 30 Dec 2007 12:56:48 -0800
On Dec 30, 2007, at 12:20 PM, Mike Abdullah wrote:
That should work as far as I can see, but you've got the selector
wrong. It's:
[textView performSelectorOnMainThread:@selector(setString:)
withObject:contentString waitUntilDone:YES]
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:
[obj performSelectorOnMainThread: @selector(foo) withObject: nil
waitUntilDone: YES];
...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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden