iPhone: Interface Builder leaks memory?
Posted
by Stefan Klumpp
on Stack Overflow
See other posts from Stack Overflow
or by Stefan Klumpp
Published on 2010-04-28T14:32:14Z
Indexed on
2010/04/28
14:43 UTC
Read the original article
Hit count: 296
I have been working on an iPhone project, where we created all the user interface programmatically in code. Now I'm going to start a new iPhone project and thinking of using Interface Builder instead, because it has been recommended to me as being a very useful tool, creating less headache than writing everything in code and in general much faster (regarding development time).
However, my team members have some concerns due to previous problems with using Interface Builder and resulting memory leaks. Therefor they suggest building everything in code again. I don't know where these concerns come from, but maybe someone with more experience than we have can give some insight on that topic.
Doing a simple Google search doesn't really provide any information proofing that there are any problems with memory leaks created by the Interface Builder itself.
© Stack Overflow or respective owner