I seem to recall back circa last century in Xcode 3.1.3 that when a view 
controller was instantiated that part of the loading/bootstrapping of the view 
controller was that it would automatically look for an XIB of the same name as 
the viewController and load that on the Mac OS.  

On iOS, I recall that it would look for a xib of the same name as the view 
controller for the iPhone and then it would look for an xib with the same name 
of the view controller and "~iPhone.xib" and it would automatically look for an 
xib that was the same name of the view controller + "~iPad.xib".

Now, I can't seem to find any of the docs that mentioned this and I'm trying to 
verify this functionality and where it is called from by stepping through the 
debugger at the view controller's initialization.

This is where I need some help.

I'm looking for effective ways of either setting a breakpoint on keywords or 
internal classes that would indicate where this happens so I can explain how 
and where this happens to the rest of the team.

Are there any techniques in using the debugger that would help in this effort?

Are there any recommended classes in the framework where setting breakpoints on 
the headers would be useful?

Would it make sense to add methods from super to my view controller that are 
part of the init process that would shed some light on this?

I'm not seeing a breakdown of the VC initialization process and methods called 
in the VC programming guide or the class reference.

Are there any better places to look?  Is there an clear method to set a 
breakpoint when an XIB is loaded?  I've tried setting breakpoints in the bundle 
class's load method to no avail.

Thanks for pointing me to the right direction.

Alex Zavatone
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to