|
From: | Quentin Mathé |
Subject: | Re: NSBundle patches breaks some app |
Date: | Thu, 11 May 2006 11:03:52 +0200 |
Le 10 mai 06 à 15:21, Richard Frith-Macdonald a écrit :
On 10 May 2006, at 13:12, Quentin Mathé wrote:Le 10 mai 06 à 13:21, Richard Frith-Macdonald a écrit :had base and gui built without 'debug' initially when I observed the issue. Now in my latest setup, I compiled gui with 'debug', but base is still compiled without. Take note I didn't try to run an application compiled without 'debug', linking a base version built with 'debug'.I found it, and added a fix to NSBundleAdditions.m in the gui library ...
Thank you for this correction. It fix the problem I had, everything is loading fine now.
It was asking for the bundle for the NSApplication class, and trying to load from that bundle. Previous to the NSBundle fixes, the call to bundleForClass: was returning nil, and the nib loading code fell back to using the main bundle of the application.
ok.I just would like to mention it would be nice that you add comments to the related code in NSBundleAdditions, because I can understand it right now, but I'm pretty sure I won't in two months from now. Probably something inspired by your ChangeLog entry.
I've modified it so that, if the nib/gorm file is not found in the bundle for the class, it tries the main bundle of the application as well.
I think that's the right order to handle it (to answer your ChangeLog entry).
What I don't understand is why the problem didn't show up when things were built with debug=yes ?
Me neither I admit. I would like know, although it isn't the first time I observe a bug I cannot reproduce with debug=yes.
Thanks Quentin. -- Quentin Mathé qmathe@club-internet.fr
[Prev in Thread] | Current Thread | [Next in Thread] |