On Apr 1, 2010, at 11:25 AM, Andreas Grosam wrote:
> Still, I see an advantage when using protocols. The argument of changing
> interfaces does not count IMO, since Categories are prone to changes as well.
> If sometimes the category get removed or the methods get changed, my code
> will not run
On Apr 1, 2010, at 7:42 PM, Greg Parker wrote:
> On Apr 1, 2010, at 10:32 AM, Andreas Grosam wrote:
> It would be possible to declare a new NSThreadPerformingObject protocol that
> built upon the NSObject protocol. You could do this yourself if you like. But
> even that would only work for one
On Apr 1, 2010, at 10:32 AM, Andreas Grosam wrote:
Having said this, I do think, the performSelector:onThread and
performSelectorOnMainThread methods should be declared in a protocol
- and not just within a category. What does it mean, when the
compiler does not find essential methods relate
performSelector:onThread:withObject:waitUntilDone: is a method on NSObject, not
.
HTH,
Dave
On Apr 1, 2010, at 11:32 AM, Andreas Grosam wrote:
> I get this warning
>
> "performSelector:onThread:withObject:waitUntilDone:' not found in protocol(s)"
>
> when
I get this warning
"performSelector:onThread:withObject:waitUntilDone:' not found in protocol(s)"
when the receiver of the message is declared as:
id viewDelegate;
and SomeViewDelegate is declared as a protocol:
@protocol SomeViewDelegate
...
@end
for example:
- (voi
