Thanks For the reply Kyle
On 16 May 2008, at 06:43, Kyle Sluder wrote:
On Thu, May 15, 2008 at 5:30 PM, <[EMAIL PROTECTED]> wrote:
It would seem that NSDictionaryController keys have to be strings.
Yes. It is very common that, despite NSDictionary accepting any
object as a key, you must use NSString keys.
So the sorting of numeric string keys is always going to be
alphabetic.
Not true. See -[NSString compare:options:] with the NSNumericSearch
option.
Good to be directed towards this method. I had missed the
NSNumericSearch option.
My solution was to discard NSDictionaryController and create a
proxy object
containing two properties:
I would instead suggest subclassing NSDictionaryController and
overriding -arrangedObjects. The naive implementation would call
super's implementation and return a sorted version of the result. The
published interface says that -arrangedObjects returns id, but the
documentation says that it returns an array, so I would feel
reasonably safe treating the return value as an NSArray.
That's a much more classy solution than my proxy object array kludge.
--Kyle Sluder
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
