FROM : Jonathan Jackel
DATE : Sun Dec 12 07:24:44 2004
Subclassing in Cocoa generally is not the preferred solution.
isEditable is just the getter accessor; setEditable is the setter (for
table columns anyway). If you have a setter, why would you go to the
trouble of subclassing just to set the value?
If a method is intended to be overridden by subclasses, the docs say
so, e.g., -[NSCoder containsValueForKey:]
Jonathan
On Dec 11, 2004, at 4:23 PM, Danny Swarzman wrote:
> In order to make a NSTableView or NSTableColumn not editable do you:
>
> - Call setEditable?
> - Override isEditable?
>
> In general is there a way to determine from the documentation which
> methods are intended to be called and which are to be overridden?
>
> -Danny
DATE : Sun Dec 12 07:24:44 2004
Subclassing in Cocoa generally is not the preferred solution.
isEditable is just the getter accessor; setEditable is the setter (for
table columns anyway). If you have a setter, why would you go to the
trouble of subclassing just to set the value?
If a method is intended to be overridden by subclasses, the docs say
so, e.g., -[NSCoder containsValueForKey:]
Jonathan
On Dec 11, 2004, at 4:23 PM, Danny Swarzman wrote:
> In order to make a NSTableView or NSTableColumn not editable do you:
>
> - Call setEditable?
> - Override isEditable?
>
> In general is there a way to determine from the documentation which
> methods are intended to be called and which are to be overridden?
>
> -Danny
| Related mails | Author | Date |
|---|---|---|
| Danny Swarzman | Dec 11, 22:23 | |
| Jonathan Jackel | Dec 12, 07:24 |






Cocoa mail archive

