On May 31, 2009, at 8:04 AM, Pierre Berloquin wrote:
Also I follow your advice about retaining loopholes and use
-(void)setViewController:(UIViewController *) vc{
theViewController = vc;
}
So the warning remains puzzling. Note that it's displayed on the sub
view .m
page only, after the call line, not after the mention "Succeeded".
I think you're under the impression that the recommendation to avoid
retain cycles is somehow related to the warning you received. It is
not. I made that recommendation as a general statement since you're
doing something that could very easily cause retain cycles (namely,
having a view store a pointer to its view controller).
On May 31, 2009, at 11:30 AM, Pierre Berloquin wrote:
I think I solved the warning problem. I suspected my folder logic
was wrong
so I cleaned it up, taking all class files from the project and
adding them
back one by one. And it works fine, no warning anywhere !I had a
duplicate
controller I had created by mistake and I thought I had gotten rid of.
Ok, that might be it. If it works now, great.
Thanks
Welcome.
Wagner
_______________________________________________
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
