FROM : jonathan@mugginsoft.com
DATE : Fri May 16 14:03:38 2008
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_removed>> 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
DATE : Fri May 16 14:03:38 2008
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_removed>> 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
| Related mails | Author | Date |
|---|---|---|
| jonathan@mugginsof… | May 13, 13:25 | |
| jonathan | May 15, 23:30 | |
| Kyle Sluder | May 16, 07:43 | |
| Shawn Erickson | May 16, 08:05 | |
| jonathan@mugginsof… | May 16, 14:03 | |
| jonathan@mugginsof… | May 16, 14:07 |






Cocoa mail archive

