NSCell accessor overrides being ignored?
NSCell accessor overrides being ignored?
- Subject: NSCell accessor overrides being ignored?
- From: Andrew Merenbach <email@hidden>
- Date: Sun, 5 Dec 2004 14:42:58 -0800
I am absolutely positive that this has come up on the lists before, but
am at a loss as to what my search should be. A reference to an
existing article would be greatly appreciated if my question's already
been answered.
I've noticed that, when overriding NSButtonCell, for example, I cannot
override most, if not all, of the useful accessors such as
-(BOOL)allowsMixedState or -(NSBezelStyle)bezelStyle, but instead have
to use the set*: accessors.
While I understand that this saves some AppKit overhead--with so many
controls and cells floating about, directly referring to the
internally-stored states would be more efficient--would it *truly* slow
down the system that much for the AppKit to be redesigned such that the
accessors are always referenced? It seems that from a standpoint of
consistency it makes more sense, and can be more straightforward for
subclassers (I can leave the init: method alone, for example, and
simply override the bezelStyle accessor).
With that in mind, does anyone with some inside knowledge of Apple's
modifications to the original NeXT classes know whether they (a)
originally did in fact reference all of these accessors, and (b)
whether Apple had/has in mind a goal of moving back to that once the
system is optimised enough?
Cheers,
Andrew Merenbach
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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