On Jul 15, 2011, at 02:44, Torsten Curdt wrote: > So you are saying it should be rather "Content Values" instead?
No, I can never remember which of NSPopUpButton's multitudinous binding is the correct one to use. (That's one reason I don't bother with bindings for this class. By the time I've worked out which binding to use, I could have written the code to create the menu items directly.) I was just using "Content" generically. > Hm. That's too much work for that simple popup button :) Most of the work is keeping track of whether the name properties have changed. You have to do that regardless of what solution you choose (bindings or not). If the names can't change, it's one step easier. If the array can't change either, it's a whole lot easier. I really think NSPopUpButton bindings are too obscure to use. It's not clear in the end that they save *any* code. _______________________________________________ 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
