Re: NSTokenField bug in 10.5.2?
Re: NSTokenField bug in 10.5.2?
- Subject: Re: NSTokenField bug in 10.5.2?
- From: Aki Inoue <email@hidden>
- Date: Wed, 13 Feb 2008 15:26:16 -0800
Thanks for the definitive statement on this. Will the docs be
updated to explain this? Should I file a radar for it (or update the
existing one)?
Please file a bug for doc update.
Thanks,
Aki
On 2008/02/13, at 15:21, Paul Kim wrote:
On Feb 13, 2008, at 5:56 PM, Aki Inoue wrote:
It appears the ML figured it out.
Yes, we did trim whitespace in 10.4, and the behavior change in
10.5 caused binary compatibility problems with various applications.
We rolled out a solution for the binary compatibility problem in
10.5.2.
The logic to determine whether or not to apply the auto whitespace
trimming is:
- trims if linked against 10.4.x binary
- trims if linked against 10.5.x binary and the delegate doesn't
implement -tokenField:representedObjectForEditingString:
- does not trims if linked against 10.5.x binary and the delegate
implements -tokenField:representedObjectForEditingString:
Aki
Thanks for the definitive statement on this. Will the docs be
updated to explain this? Should I file a radar for it (or update the
existing one)?
Paul Kim
_______________________________________________
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
_______________________________________________
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