On Aug 13, 2014, at 4:04 AM, Jonathan Taylor <[email protected]> wrote:
>> I would create a class, say, SignalChannel, with "name" (for description, >> but we may not ant to use "description" for obvious reasons...) and >> "channelID" properties. I would then populate the NSPopupButtonCell with >> SignalChannel objects. This will abstract the model from the view, which is >> better form anyway. > > Ah, I've worked out the underlying problem I've been having. I had been > trying things along these lines and completely failing to get the popup menu > to populate correctly. It was working for a standalone popup but not within > the table, and I was assuming I was doing something wrong and/or it was more > complex than I realised, and had basically decided not to continue stumbling > around trying to make it work. Then I found this: > http://stackoverflow.com/questions/14708947/nspopupbutton-in-view-based-nstableview-getting-bindings-to-work > which describes what seems to be a bug in the implementation, along with the > workaround (binding to an outlet property on the file's owner, rather than > directly to the array controller). Weird. That link refers to a view-based table view, which is a different animal altogether. Is your table view cell or view based? It makes a big difference... Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business" _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
