Re: Why would a defined selector not be found at runtime?
Re: Why would a defined selector not be found at runtime?
- Subject: Re: Why would a defined selector not be found at runtime?
- From: Scott Thompson <email@hidden>
- Date: Thu, 12 May 2005 14:25:24 -0500
On May 12, 2005, at 2:13 PM, Ken Tozier wrote:
Well I figured it out, sort of.
When I renamed the class to UIDisclosureButtonCell, it works.
Anyone know of a reason why changing the class name would have such
a dramatic effect? Does Apple reserve the "NS" prefix for itself
and behave differently when classes have that prefix? Very bizarre.
It could be the case that the OS already has a class named
NSDisclosureButtonCell. It may not be part of the public interface
(so it wouldn't show up in the headers), but it might still exist.
That's WHY Apple "reserves" the NS prefix. That prefix is designed
to avoid name space collisions.
Scott.
_______________________________________________
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