On Jun 20, 2012, at 11:32 PM, Michael de Haan wrote: > Is the approach therefore to create the bindings to the databases, as well as > the searchField in code ( as opposed to IB)?
You can do that. It's not hard to set and remove bindings in code. Another possibility is to create your own class as an intermediary. It observes one database or the other and exposes the data as observable properties. You then instantiate one of those in the nib and bind the UI elements to it. Then you can switch the object's state from viewing one database to the other (maybe by changing an "inputSource" property?) This is also a good approach because it decouples your UI implementation from the details of how you get the data to display in it. —Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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
