Sorry but that just doesn't make sense. The empty string and nil are just not the same thing. If you set a text field's text to the empty string, you will get an empty string, you will not get nil. The only way I can imagine this happening is if the text field is nil at the point you set the empty (or any other) string into it so you didn't really set anything at all.
On May 9, 2012, at 11:18 PM, Fritz Anderson wrote: > In my experience, setting a text field to the empty string will have it > return nil when you access the string. I can't quite relate it to the code > path you're following, but it may be a clue. > > — F > > On 8 May 2012, at 10:48 PM, Antonio Nunes wrote: > >> Why do you recommend against using integerValue? For me it would make more >> sense to always use integerValue, especially now that I can set the value to >> 0 to show an empty text field, since we're conceptually representing numbers >> here, not strings. > > > _______________________________________________ > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org > > This email sent to r...@rols.org _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
