> On Thu, Jul 17, 2008 at 7:52 PM, Ken Thomases <[EMAIL PROTECTED]> wrote: >>> How can I build one class to handle both??? >> >> You sound very vexed by this question, but the answer seems self-evident to >> me. You just do. It's totally up to you what your classes do and how you >> use them. Nobody's standing in your way. > > Surprisingly, this sort of problem comes up fairly frequently, where > an inexperienced guy doesn't know where to start, and an experienced > guy doesn't even see where the problem is. Just do it! He says. But > how?
I think part of the issue here is interacting with System Preferences is more limiting than a full application (plus some other issues that I won't go into). Based on a few of the suggestions here, I have decided on a decent solution where I can get the tab A functionality separated from the rest of the logic. Thanks, Trygve _______________________________________________ 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 [EMAIL PROTECTED]
