Yea that is exactly how I have it currently as I described in my mail.
But to maintain that has unnecessarily extra steps. My Controller
extends my own custom controller class (which extends
UIViewController) which adds the common functionality I require to the
types of apps I'm building. But there is no way my view (which
contains x amount of sliders, labels, and switches specific to the
application laid out manually the way I want them to look) and model
(parameters very specific to this application) are reusable. Which is
why my question was about the performance of reading from the controls
directly.
On 20 Feb 2009, at 03:30, Michael Ash wrote:
Your model should not be talking directly to your view. Instead, your
controller should set properties on the model when the UI changes, and
then the model can use its own properties directly.
_______________________________________________
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
