Gah! That was it - seems I actually added a [super awakeFromNib] at
some point to one of my classes during the refactoring for reasons
that escape me now. Removing it fixes the issue.
Thanks for the help guys (off-list too).
--Graham
On 26/10/2009, at 2:53 AM, Jim Correia wrote:
On Oct 2
On Oct 25, 2009, at 12:22 PM, Roland King wrote:
Where's that documented??? I looked for that when I saw the original
question. For iPhone it's documented under NSObject UIKit Additions
Reference, for 10.6 it's under NSNibAwakingProtocol which doesn't
show up anywhere as an implemented prot
Where's that documented??? I looked for that when I saw the original
question. For iPhone it's documented under NSObject UIKit Additions
Reference, for 10.6 it's under NSNibAwakingProtocol which doesn't show
up anywhere as an implemented protocol of NSObject.
I'm sure you're right but I've
On Oct 25, 2009, at 7:53 AM, Graham Cox wrote:
Then, running on 10.5.(8) I stared to get an error that the object
did not respond to -
awakeFromNib. I'd not previously seen this error until I refactored
my code. Sure enough my new base class and its new fork don't
implement awakeFromNib b
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 th
Well the documentation for 10.6 does say that awakeFromNib is called
only if the receiver responds to it, I don't have the leopard docs on
my machine at the moment so I don't know what that says.
Are these new objects really new classes which weren't in the NIBs
before or are classes which
I have, or rather had, a problem. I've solved it but I'm still not
sure why the problem is there in the first place.
I have a bunch of controller classes which have a common base class,
and this in turn subclasses NSObject. Recently I factored out some
code into an even more primitive base
