On 25/10/2009, at 11:24 PM, Roland King wrote:
Are these new objects really new classes which weren't in the NIBs before or are classes which were always in the NIB, but where you've now changed the implementation of the class to use the new refactored code? My thought was that the NIBs themselves might contain hints about whether to call awakeFromNib compiled in and the NIBs themselves were not recompiled as their content objects appear to be the same. If that is possible, then touching some of them and forcing them to recompile might sort it out.
It's both - there are existing classes which now have an extra ancestor, plus instances of the new class that only inherit the new base class. Only the new class is throwing the error - though because it throws an exception it might not be getting as far as the others - I need to check that. All the nibs have been fully recompiled however, as I did a clean build.
--Graham _______________________________________________ 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
