Re: Strange Core Data problem after upgrade
Re: Strange Core Data problem after upgrade
- Subject: Re: Strange Core Data problem after upgrade
- From: Rui Pacheco <email@hidden>
- Date: Thu, 8 Oct 2009 12:49:06 +0100
Hi,
Problem A,
Yes, all classes are set correctly in the data modeller.
Also, regarding problem B, this is getting stranger.
If I set the type of the variable to int 32 in the modeller and NSNumber in
the class and then assign it a value using [entity value:forKey] it works
just fine. But if I add an NSTextField to IB and bind it to that property,
it fails with the stringValue error.
If, on the other hand, I set the type to string, on the modeller and on the
class, IB will work just fine.
This makes me think that somewhere IB isn't converting from string to
integer, but I don't remember having to set that manually.
Rui
2009/10/7 Volker in Lists <email@hidden>
> Hi,
>
> problem A:
> have you made sure you have set the class in the data modeler correctly for
> that ManagedObject? When googling for your error message I do receive such
> problems that were fixed by setting the proper custom class name.
>
> Cheers,
> Volker
>
--
Best regards,
Rui Pacheco
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden