Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Advice On Subclass vs. Delegate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Advice On Subclass vs. Delegate

Subject: Re: Advice On Subclass vs. Delegate
From: Jerry Krinock <email@hidden>
Date: Sat, 14 Nov 2009 05:41:08 -0800


On 2009 Nov 12, at 18:54, s.ross wrote:

That suggests to me that subclassing NSTextField and allowing a single controller to register a callback would be the right way to go, but I'm struggling with how to specify *which* text field

I don't understand the question. You subclass class definitions, not instances. The thing you would subclass would be NSTextField. Your subclass will be a "sister" of, for example, NSSecureTextField.

and whether my design idea is even sound.


other than that, it looks like you know what you are doing.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


Follow-Ups:

Re: Advice On Subclass vs. Delegate
From: "s.ross" <email@hidden>


References:  
  >Advice On Subclass vs. Delegate (From: "s.ross" <email@hidden>)




Prev by Date:
Re: Stack-based C++ class to wrap NSAutoreleasePool

Next by Date:
Re: Using HTML form in cocoa app

Previous by thread:
Advice On Subclass vs. Delegate

Next by thread:
Re: Advice On Subclass vs. Delegate

Index(es):

Date
Thread