Re: Accessing interface elements (iPhone vs Mac)

2009-01-21 Thread Adam Venturella
I also just found this bit in the docs: http://developer.apple.com/documentation/Cocoa/Conceptual/LoadingResources/CocoaNibs/chapter_3_section_4.html#//apple_ref/doc/uid/1051i-CH4-SW18 Nib Object Retention iPhone OS - managed memory model Objects in the nib file are created with a retain cou

Re: Accessing interface elements (iPhone vs Mac)

2009-01-21 Thread Dave DeLong
On Jan 21, 2009, at 11:25 AM, Adam Venturella wrote: I have seen this same behavior too, creating @properties for IBOutlets on the iPhone. I have yet to run into a problem not @property/@synthsizeing my Outlets on the iPhone, everything seems to work just fine if you don't. So am I missing

Re: Accessing interface elements (iPhone vs Mac)

2009-01-21 Thread Adam Venturella
Answered my own question re the dealloc here: Important: You are responsible for releasing the top-level objects of any nib files you load when you are finished with those objects. Failure to do so is a cause of memory leaks in many applications. After releasing the top-level objects, it is a good

Re: Accessing interface elements (iPhone vs Mac)

2009-01-21 Thread Adam Venturella
I have seen this same behavior too, creating @properties for IBOutlets on the iPhone. I have yet to run into a problem not @property/@synthsizeing my Outlets on the iPhone, everything seems to work just fine if you don't. So am I missing something? And am I correct in assuming you would then be

Re: Accessing interface elements (iPhone vs Mac)

2009-01-21 Thread Shawn Erickson
On Tue, Jan 20, 2009 at 5:30 PM, Graham Cox wrote: > When the nib is loaded, the accessor is used rather than setting the ivar > directly (as per Mac) To be clear NIB loading on Mac OS X will use a setter if one exists (assuming a name match)... Outlet connections In Mac OS X, the nib-loading

Re: Accessing interface elements (iPhone vs Mac)

2009-01-20 Thread mmalc Crawford
I omitted: mmalc ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the

Re: Accessing interface elements (iPhone vs Mac)

2009-01-20 Thread mmalc Crawford
On Jan 20, 2009, at 12:41 PM, Ashley Perrien wrote: I'm currently fairly comfortable with Mac development but still struggling to learn iPhone. I'm seeing differences in how things are coded and I'm not seeing many explanations as to why the difference. For instance, on the Mac, in Interfa

Re: Accessing interface elements (iPhone vs Mac)

2009-01-20 Thread Graham Cox
On 21 Jan 2009, at 7:41 am, Ashley Perrien wrote: I believe I've tried it and the property and synthesize are not NECESSARY for it all to work; so is having it in there of some kind of benefit for the iPhone or is it just a quirk of how developer X likes to do things? I've seen some discus