Re: I think I have found a big bug in NSBrowser
Re: I think I have found a big bug in NSBrowser
- Subject: Re: I think I have found a big bug in NSBrowser
- From: Hamish Allan <email@hidden>
- Date: Mon, 30 Jan 2006 17:00:46 +0000
On 27 Jan 2006, at 21:20, Andre wrote:
Hmm, Did you set it to entity mode or class mode? In class mode,
its using NSDictionary so I just bind the NSBrowser to
NSTreeController using the following
Oops, for some reason I was binding ContentValues straight to
arrangedObjects. It's working now.
I have also implemented a couple of workarounds for NSBrowser
bindings bugs relating to selection indexes. They are available in a
demonstration project here:
http://igor.gold.ac.uk/~map01ra/assorted/NSBrowserBugWorkarounds.zip
Most of them are implemented in the eponymous subclass of NSBrowser,
but NB one of them is in setIndexPaths: in the detail array
controller's object class. Unfortunately I have not yet created a
workaround for NSBrowserBinder's eagerness to populate cells for
every row in each column rather than just for those which are visible.
Anyway, I am very glad to know that there is at least ONE other
person in the world using NSBrowser bindings :) I was somewhat
dismayed to read Apple's recent job advert for Finder, because I was
really hoping that it would be written using Cocoa, which might have
meant that NSBrowser bindings were in rather more active development.
Alas, it would appear that this is not the case.
Thanks,
Hamish
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden