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: Andre <email@hidden>
- Date: Mon, 30 Jan 2006 12:14:14 -0800
On 平成 18/01/30, at 9:00, Hamish Allan wrote:
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.
Cool, thanks, thats an even better file browser sample code than the
SinpleBrowser example. Very nice.
Anyway, I am very glad to know that there is at least ONE other
person in the world using NSBrowser bindings :)
Yea, its so nice to use bindings, the only thing is, that with
NSBrowser, I'm finding that to make up for the lost functionality,
I'm writing just as much code........... as before 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.
Yea, I have little faith in the finder being anything more than what
it is... the part that really kills is the part about honing one's
hobby skills working on the finder.... @_@
I think, PF4, basically, a one man job (using NSBrowser subclass I
believe) blows the whole "finder team" to bits. But, thats MHO.
I'm thinking about just ditching NSBrowser all together. If I had
time, I would use NSTableColumns and or even NSTableViews, so I can
sort the content of the browser,in each column. Also, handling the
bindings my self, I can set the representedObject and the objectValue
of the cells... currently NSBrowser doesn't set the represented
object.... if I had time anyways...
Thanks,
Hamish
Andre
email@hidden
_______________________________________________
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