Hi all,

I'm currently working my way through the book using XCode 4. So far so good, but I do have a question now.
In the How it works explanation of the example on page 95 the author writes that you need to override the viewDidLoad method to programmatically create your view during runtime.
However in the example in chapter 3 on dynamically adding views he overrides the loadView method to build up the user interface.

Now I tried doing the same thing in this project. So instead of using viewDidLoad (works) I implement loadView. In that case I get a EXC_BAD_ACCESS error on this line: button.frame = frame;

When I add a call to the superclass in the first line of loadView, like this: [super loadView]; I no longer receive this error, but the author doesn't use this in the chapter 3 example. So my question is: what's the difference between those two methods and why does the author pick one over the other in those two examples?

Ruben.

Have you read the documentation for -loadView? If not, check it out, and if you still have questions, I can try to expand on it.

Bob

Hi Bob,

I haven't, but now I have. So if I understand correctly if you override loadView you need to create an actual view object and populate that with subviews. And viewDidLoad is called after loadView, so at that point the view is already loaded and you can add subviews to it.

What I don't get though is why I got the EXC_BAD_ACCESS error on that specific line (button.frame = frame) and why I don't get it when I first call the superclass implementation of loadView.

Thanks!

Ruben.

Send me a copy of the project that is generating the error. It will be easier for me to diagnose if I don't have to speculate or make any assumptions about your code.
[email protected]

Bob