Re: [iPhone 3.0; XCode 3.1.3] Question about when views are available for manipulation.

2009-08-19 Thread Brian Bruinewoud
Resending because I never saw this appear in the list. On 10/08/2009, at 21:51 , Brian Bruinewoud wrote: I found the motivating example for this thread. Files are: http://media.pragprog.com/titles/amiphd/code/FileIO/FilesystemExplorer/Classes/DirectoryViewController.m http://media.pragprog.com

Re: [iPhone 3.0; XCode 3.1.3] Question about when views are available for manipulation.

2009-08-10 Thread Brian Bruinewoud
I found the motivating example for this thread. Files are: http://media.pragprog.com/titles/amiphd/code/FileIO/FilesystemExplorer/Classes/DirectoryViewController.m http://media.pragprog.com/titles/amiphd/code/FileIO/FilesystemExplorer/Classes/FileOverviewViewController.m For this book: http://bo

Re: [iPhone 3.0; XCode 3.1.3] Question about when views are available for manipulation.

2009-08-10 Thread Brian Bruinewoud
All, Thanks for the responses so far. I'm getting there. If I may quote Henry McGilton (Boulevardier) out of order: On 10/08/2009, at 15:02 , Henry McGilton (Boulevardier) wrote: Similar situation with the call to makeKeyAndVisible - I've seen samples of applicationDidFinishLaunching where m

Re: [iPhone 3.0; XCode 3.1.3] Question about when views are available for manipulation.

2009-08-09 Thread Henry McGilton (Boulevardier)
On Aug 8, 2009, at 1:23 AM, Brian Bruinewoud wrote: Hi, I'm a little confused about how this code works: MyController *myController = [[ myController alloc ] initWithNibName: @"myView" bundle: nil ]; [[ self navigationController ] pushViewController: myController animated: Y

Re: [iPhone 3.0; XCode 3.1.3] Question about when views are available for manipulation.

2009-08-09 Thread Paul Collins
On Sat, Aug 8, 2009 at 10:40 PM, Brian Bruinewoud wrote: > as it could be? What would be the better way to achieve this? > > At a guess to my second question: I suppose the new view should call on > methods/properties of its File's Owner to discover what it needs to display. > I haven't tried this

Re: [iPhone 3.0; XCode 3.1.3] Question about when views are available for manipulation.

2009-08-08 Thread Brian Bruinewoud
Thanks for the replies so far. Lazy loading makes sense. But what you say bellow suggests that the code in my original post is broken - or at least, potentially broken. The design comes from a beta version "iPhone SDK Development" by Bill Dudney and Chris Adamson. They use something very s

Re: [iPhone 3.0; XCode 3.1.3] Question about when views are available for manipulation.

2009-08-08 Thread Luke the Hiesterman
On Aug 8, 2009, at 1:23 AM, Brian Bruinewoud wrote: Why doesn't initWithNibName create and bind all the IBOutlets before it returns? Is the view guaranteed to be visible after pushViewController returns? Or is it still animating on another thread? Or is the request to display the view merely

Re: [iPhone 3.0; XCode 3.1.3] Question about when views are available for manipulation.

2009-08-08 Thread Kyle Sluder
On Aug 8, 2009, at 1:23 AM, Brian Bruinewoud wrote: Why doesn't initWithNibName create and bind all the IBOutlets before it returns? Because it's good to be lazy. I'm not an iPhone developer, but I'm willing to wager that the nib isn't actually loaded until the view itself is requested,

[iPhone 3.0; XCode 3.1.3] Question about when views are available for manipulation.

2009-08-08 Thread Brian Bruinewoud
Hi, I'm a little confused about how this code works: MyController *myController = [[ myController alloc ] initWithNibName: @"myView" bundle: nil ]; [[ self navigationController ] pushViewController: myController animated: YES ]; myController.myProperty = itsValue;