On Jul 29, 2009, at 11:24 AM, Jim Correia wrote:
On Jul 29, 2009, at 1:09 AM, Alexander Heinz wrote:
I've got an NSArrayController subclass with a computed property:
@property (readonly) BOOL canRemoveSelection;
(This basically adds some application-specific checks to the
canRemove: prope
On Jul 29, 2009, at 1:09 AM, Alexander Heinz wrote:
I've got an NSArrayController subclass with a computed property:
@property (readonly) BOOL canRemoveSelection;
(This basically adds some application-specific checks to the
canRemove: property, so that I can bind a "remove" button in
Inter
On 29 Jul 2009, at 06:09, Alexander Heinz wrote:
Hello all,
I've got an NSArrayController subclass with a computed property:
@property (readonly) BOOL canRemoveSelection;
(This basically adds some application-specific checks to the
canRemove: property, so that I can bind a "remove" button
On Jul 28, 2009, at 10:40 PM, Kyle Sluder wrote:
On Jul 28, 2009, at 10:09 PM, Alexander Heinz > wrote:
(This basically adds some application-specific checks to the
canRemove: property, so that I can bind a "remove" button in
Interface Builder.)
Question: why aren't you just overriding -
On Jul 28, 2009, at 10:09 PM, Alexander Heinz
wrote:
(This basically adds some application-specific checks to the
canRemove: property, so that I can bind a "remove" button in
Interface Builder.)
Question: why aren't you just overriding -canRemove?
However, the accessor for the property
I may not have made myself clear enough: I need objects bound to this
property to be notified whenever the selection of the array controller
changes, much like the existing "canAdd:" and "canRemove:" properties
of NSArrayController. This property has nothing to do with whether or
not the ar
Hello all,
I've got an NSArrayController subclass with a computed property:
@property (readonly) BOOL canRemoveSelection;
(This basically adds some application-specific checks to the
canRemove: property, so that I can bind a "remove" button in Interface
Builder.)
I want the property to be
