Temporarily disabling bindings for performance?
Temporarily disabling bindings for performance?
- Subject: Temporarily disabling bindings for performance?
- From: Kai Brüning <email@hidden>
- Date: Sun, 16 Dec 2007 11:43:43 +0100
Hi,
lets assume a pretty standard master-detail interface implemented
with bindings.
Now there are multiple variants of the detail part, separated into
different views which are exchanged against each other on user
request or depending on the selection in the master list.
Is there an (easy) way to disable the bindings in the currently
unused views? To my understanding these bindings stay live and eat
CPU cycles even while a container view with the bound controls is not
installed in a window.
One approach would be to put each view in a separate nib and unload
it when not in use. But in some cases the view to use depends on the
selection in the master list, therefore the used view can rapidly
change when the user iterates through the master list. I would
therefore prefer to keep the views in memory once loaded.
I do not expect real performance problems in the case at hand, but
nevertheless I do not like the idea of a lot of useless activity
taking place.
Thanks
Kai
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden