On Thu, 2 Dec 2010 06:38:31 -0600, James Cicenia said:
>Yes .. but why did it like it prior to my upgrade?
>
Don't confuse the compiler with the runtime. You can put anything past the
compiler. What matters is what's true at runtime. The crash log suggests that
you are not sending the message s
Yes .. but why did it like it prior to my upgrade?
Hmmm, let me check the NIB. I realized that was what was wrong.. somewhere it
is not getting PersonaDetailView.
Thanks
James
On Dec 2, 2010, at 6:26 AM, Roland King wrote:
> ok. so UIView doesn't have a setController method (according to my de
ok. so UIView doesn't have a setController method (according to my developer
docs) and you're sending it that message so it doesn't like it. Can I assume
that setController is a method you defined on PersonaDetailView? If so it seems
the thing you're sending it to isn't actually a PersonaDetail
hmm, yes... but still it works with my XCode3.2.4 with 4.1 vs now with 3.3.5
and 4.2
2010-12-02 06:11:40.705 CoinStar[31673:207] *** Terminating app due to uncaught
exception 'NSInvalidArgumentException', reason: '-[UIView setController:]:
unrecognized selector sent to instance 0x9814950'
***
Runtime doesn't care about casts, you have what you have, it is what it is,
that cast only shuts up the compiler.
What's the real error and real code.
On 02-Dec-2010, at 7:56 PM, James Cicenia wrote:
> ((PersonaDetailView*)self.view).controller = self;
>
> This fails at runtime but only in 4
((PersonaDetailView*)self.view).controller = self;
This fails at runtime but only in 4.2. Why ?
It doesn't sense the typecast and thinks it is only a UIView.
Thanks
James
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admi
