I meant to ask what the tradeoffs are between declaring the UIWindow object
as an instance variable in the AppDelegate vs. as a local object in
-applicationDidFinishLaunching:
The specific example I'd mentioned was from Erica Sadun's book, and looking
at Apple's sample code, and the code that XCode generates, it seems that the
UIWindow object is typically declared as an instance variable in the
AppDelegate and seems the way to go (as opposed to Erica Sadun's example of
using a local UIWindow object).
On Sat, Dec 13, 2008 at 6:34 PM, Debajit Adhikary <deba...@debajit.com>wrote:
> When you create an iPhone app, in the AppDelegate, why is the
> UIWindow created locally within -applicationDidFinishLaunching and not
> declared
> as an ivar? The functionality does not seem to change either way. I'd
> like to know how one approach is better than the other.
>
> What I presume is that the window object really doesn't need to be accessed
> from outside later. But doesn't declaring it as an ivar make it more
> accessible from the "outside" allowing greater application extensibility?
>
> @implementation AppDelegate
>
> - (void) applicationDidFinishLaunching:(UIApplication*) application
> {
> UIWindow* window = ... ;
> [window addSubView: ...];
> [window makeKeyAndVisible];
> }
>
> ...
> @end
>
>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
