Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Model View Controller policy says that views can`t own data and delegate should be used to ask data from the ViewController.
But what about for exapmle UILabel? Controller talks direct to the Outlet, for example:
self.textfield.text=@”Show this text”. (There is no delegate here? UILabel is also a kind of view?)
Delegation would be unnecessarily complicated for something simple like setting text in a UILabel.
An example of breaking MVC with a UILabel would be using its text property as the only storage for a piece of data used elsewhere in your app. For example, if the app involves a person’s name and other info that are displayed with UILabels, chances are you should have a Person class as part of your Model and not use the UILabels as the exclusive storage for that info.