OK Kenrik, you're on my list.
Also, I have to say you're wrong. Some people shouldn't post on this list. You have to have a certain level of ability to be able to understand the answers to your questions. It's like going to China and learning how to ask 'where's the bathroom' but not knowing enough Chinese to understand the answer. What's the point in asking?
I worked some years ago on a beta OS that was running on alpha hardware. The OS would only boot successfully one time in three tries. You can imagine how well it ran after it did boot. My job was to write some software that ran on that OS. Let's just say it took a while and debugging was difficult. How do you think Mr Noob Developer would have done on that project?
No offense meant to Mr Noob or anyone else but if you can't be bothered to search the header files or documentation for the answers to your questions then why should I answer those simple questions? Being able to learn new things and look things up is part of this business.
Being a noob is ok, yes we all were there at one time, although for me it was probably before you were born. But you have to have the basics. You have to be able to look things up. Google is your friend. I have always been amazed at how much iPhone code is available on the net, regardless of the NDA.
One of the problems with being a noob is that you don't know what questions to ask. You don't know what's important and what's likely affecting your problem. However, you should be able to ask a sensible question. Include what you've done to try to answer the question already. Include what you think the issues are. A one sentence simple question that everyone knows the answer to just indicates that you're not trying very hard and will not garner useful answers.
Does anyone know how to remove a subview?
BOOL)animated {}
Linear Mode
