>> 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...
As it stands right now, it's view based (I switched it in InterfaceBuilder). Things seem to be working fine with that workaround. I started writing a long email to the list on the question of view- vs cell-based tables, but as is often the case, in the course of writing it I worked out the answer to my particular question at the time. I ended up with view based because Apple give clear instructions for how to bind things for them in "Table View Programming Guide for Mac". Their advice for cell-based tables is rather unhelpful, just saying that it's "very different" and you should "configure the column’s cell’s bindings". Well thanks Apple! Their instructions for view-based tables were clear, so I went with that. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
