iphone - When should uiviewcontrollers be declared as properties -


Well it has been going to annoy me for a long time so that now I will ask

when uiviewcontrollers want Can be declared as property? I noticed that in many instances uiviewcontrollers, who are pushing on a uinavigation controller and have been popped not have been declared as attributes.

I extended it and now every UIVIC controller is used inside my code. I is not declared as an asset (ACC memory is handled with caution), even My main view controller is also inside the appendix. However since the device was reporting a leak, I tried to declare it as a property ... The result is that, if the leak is still somewhere, the memory acquisition of the app has been halfway.

So now I 'm thinking ... Is my view completely wrong and should all UIVieE-controllers be declared as proprietor?

View controller views can take lots of memory, and not enough memory in the iPhone That's the spare. Maybe there is some part of the controller you want, but by the time it was rejected, I could not have needed to maintain it.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -