Re: "Selector not recognized" for existing selector : how is this possible??
Re: "Selector not recognized" for existing selector : how is this possible??
- Subject: Re: "Selector not recognized" for existing selector : how is this possible??
- From: Greg Parker <email@hidden>
- Date: Fri, 20 May 2005 11:15:56 -0400
Jonathan del Strother wrote:
> My GasLight plugin works fine for most people, but it certain cases it
> crashes, complaining of the following:
>
> -[Controller initWithVisData:]: selector not recognized [self = 0x11fea00]
>
> Now...the initWithVisData method clearly exists, because it works fine
> on most people's machines, it's in the same file as the above function,
> declare in a header file,and so on...
You may be seeing a duplicate class name collision. Your code is an
iTunes plugin, and it's using the rather generic class name "Controller".
If some other plugin or iTunes itself also defines a class named
"Controller", there will be a conflict and one of the classes will
be ignored. If some other class called "Controller" wins, it probably
won't have a -initWithVisData: method like yours.
When the Objective-C runtime detects a collision, it prints an error
message, something like "Both Foo.framework and Bar.framework have
implementations of class Controller. Using implementation from
Foo.framework". Have your users look for that message in console.log
or system.log when the plugin fails.
In general, a plugin should use a unique prefix for all of its
classes, because all Objective-C classes live in a single global
namespace. A discussion of class name collisions in preference panes:
http://developer.apple.com/documentation/UserExperience/Conceptual/PreferencePanes/Tasks/Conflicts.html#//apple_ref/doc/uid/20000706
--
Greg Parker email@hidden Runtime Wrangler
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden