On Jul 28, 2009, at 10:40 PM, Kyle Sluder wrote:
On Jul 28, 2009, at 10:09 PM, Alexander Heinz <ahei...@johnshopkins.edu
> 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?
Good point. For some reason, it hadn't occurred to me to do that.
However, I also need to add another, similar property: -canChoose
(which does something subtly different) so my problem stands.
However, the accessor for the property (i.e., "-
(BOOL)canRemoveSelection") is never called, beyond the initial call
when the object is created. As a result, the button bound to the
property never changes state.
Have you actually bound anything to the controller's
canRemoveSelection property?
Yes, I have, but I will go do a sanity check right now...
But everything else seems to make sense?
Thanks,
Alex
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
