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 14:07:32 +0100
True, that seems to be the problem.
Is this new? I've another NSTextField bound to a property of type NSNumber
that works perfectly and I'm not doing any conversion. The one that works
was added while I was still using 10.5 and the one that doesn't was added
while using 10.6.
2009/10/8 Volker in Lists <email@hidden>
> Hi,
>
> you need to add a NSNumberFormatter to the text field. Number/String
> conversion does not happen automatically.
>
> Volker
>
> Am 08.10.2009 um 13:49 schrieb Rui Pacheco:
>
>
> 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
>>
>>
>
--
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