Re: Java and Cocoa - NSTableView and NSOutlineView
Re: Java and Cocoa - NSTableView and NSOutlineView
- Subject: Re: Java and Cocoa - NSTableView and NSOutlineView
- From: Kent Smotherman <email@hidden>
- Date: Sun, 8 Jul 2001 16:01:59 -0500
Right, that's the point - the bug here must be in the java "wrapper"
for this API, I would surely think it's a trivial fix if only we had
the source =)
Kent
At 11:58 AM -0700 7/7/01, Chuck Pisula wrote:
The problem is that, YES, in these problematic cases, Cocoa keeps a
"pointer" to the data, but does not retain them. Ie. it doesn't
send an [obj retain]. There are good reasons why certain objects
are not retained (in the ObjC world).
-chuck
On Tuesday, July 3, 2001, at 12:01 PM, Kent Smotherman wrote:
I did some poking around the archives and found some suggestions that the
trouble with NSOutlineView and Java is true of some other API's in Cocoa as
well, and the argument goes like this: NSOutlineView (or whatever control is
being discussed) does not keep a reference to the objects the user code
provides and so the java garbage collector is freeing these objects if the
user code does not maintain it's own references to them. THIS CANNOT BE
TRUE! With NSOutlineView for example, the argument is basically that what is
returned from outlineViewChildForItem is not being "retained" by Cocoa. If
it were not being retained by Cocoa, what object is Cocoa passing in during
outlineViewValueForItem for example??? This can simply not be the case, the
real cause of these issues must be elsewhere. Any ideas anyone?
Kent Smotherman
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
--