Re: Objective-C++, class scope constants, name conflicts
Re: Objective-C++, class scope constants, name conflicts
- Subject: Re: Objective-C++, class scope constants, name conflicts
- From: Scott Ribe <email@hidden>
- Date: Fri, 10 Feb 2006 19:47:55 -0700
- Thread-topic: Objective-C++, class scope constants, name conflicts
> Are you aware of NSMatrix, NSTableView, NSArrayController, and
> NSTabView. All of these (and some other options too) can be used in
> different circumstances to let you use zero or one IBOutlet to access
> any number of controls difiend in IB. This way, the number of
> controls can be set in IB and only in IB.
I'm aware of them and use them, but none of them are appropriate here. Hmm,
well, actually I hadn't thought of using an NSTableView of an appropriate
height and turning off headers and both scroll bars, that might do... I'm
used to using them, like, well, real tables ;-)
> There is also "Foundation Collections Palette" that allows you to put
> the array in your IB NIB file so that your class only needs an
> IBOutlet to the array of controls. You can populate the array
> entirely within IB. Make any target/action connections in IB.
> http://www.geocities.com/kritter_cocoadev/
That sounds like the appropriate idiom to fully decouple the item count from
the code.
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden