Re: Namespace clash problem

2011-10-13 Thread Quincey Morris
On Oct 13, 2011, at 18:55 , Graham Cox wrote: > Looks like I have no choice but to change the method name for the class > method at least :( Incidentally, I've been trying to remember for months why using a class object (plus static variables) wasn't a satisfactory implementation of a singleton

Re: Namespace clash problem

2011-10-13 Thread Kyle Sluder
On Thu, Oct 13, 2011 at 6:55 PM, Graham Cox wrote: > That doesn't work, because it then complains: "warning: instance method > 'style' is being used on 'Class' which is not in the root class" Heh, looks like it picked -style instead of +style. Makes sense, I guess. The compiler's not going to lo

Re: Namespace clash problem

2011-10-13 Thread Graham Cox
That doesn't work, because it then complains: "warning: instance method 'style' is being used on 'Class' which is not in the root class" Looks like I have no choice but to change the method name for the class method at least :( --Graham On 14/10/2011, at 12:51 PM, Kyle Sluder wrote: > On T

Re: Namespace clash problem

2011-10-13 Thread Kyle Sluder
On Thu, Oct 13, 2011 at 6:32 PM, Graham Cox wrote: > The object in question is actually a class, where it has a class method > +style. But the class is passed as the 'object' parameter of a notification, > which has type id. How do I typecast that to the precise class type I'm > expecting? Usin

Re: Namespace clash problem

2011-10-13 Thread Graham Cox
Ah, that's clear, but I now see why I'm going wrong. The object in question is actually a class, where it has a class method +style. But the class is passed as the 'object' parameter of a notification, which has type id. How do I typecast that to the precise class type I'm expecting? Using (MyC

Re: Namespace clash problem

2011-10-13 Thread Kyle Sluder
On Thu, Oct 13, 2011 at 4:29 PM, Graham Cox wrote: > Typecasting the return type to be the explicit object type I expect does not > eliminate the warning. You need to typecast the recipient, not the return type. --Kyle Sluder ___ Cocoa-dev mailing li

Re: Namespace clash problem

2011-10-13 Thread Jens Alfke
On Oct 13, 2011, at 4:29 PM, Graham Cox wrote: > When I go into this warning, it further states it's using > [NSProgressIndicator style] instead of my own declared method style which > exists in many different objects (and which would be correct). This only happens when calling -style on an un

Namespace clash problem

2011-10-13 Thread Graham Cox
I just updated to Xcode 4.2 from 4.1, and I'm getting a new warning when I compile: "Multiple methods named 'style' found" When I go into this warning, it further states it's using [NSProgressIndicator style] instead of my own declared method style which exists in many different objects (and wh