Re: JavaBridge
Re: JavaBridge
- Subject: Re: JavaBridge
- From: Julien Dufour <email@hidden>
- Date: Wed, 5 Dec 2001 15:57:43 +0100
Definitely me too? ;-)
Here is an example one problem I've had:
http://www.vineyardenterprise.com/BlackMoon.tar.gz
This is an initial attempt to port the SWT toolkit from Eclipse
(www.eclipse.org) to the Mac. When you run the application everything
is
fine until you try to resize the window quickly and repeatedly. Just
build
& run the application, grab the resize control, jiggle your mouse, and
watch
it crash.
I got the same problem. It is really strange... I have no answer for
you, sorry.
However, I have two more pieces of information since a posted my fist
mail:
- Cocoa objects are backed by objc objects, and ObjectiveC memory rules
apply to them. In many cases, when you give a reference to a cocoa
object A, the referenced object B will not by retained by A. So, if you
don't keep another reference to B in your code, the Java GC will simply
free it as it should, and when A tries to use it, your app crashes.
- PB has became a major player to me... The day after I posted, I
cleaned and rebuilt my application (once again) without having changed
anything, and it worked perfectly! I often did the same before, but this
time was the good one. I'm still looking for an explanation...
Hope it will help.
The problem appeared when I started using the Notification Center in the
Shell class of the project.
[delete]
I've been reading Cocoa documentation quite thoroughly and I'm not
having
any luck learning about how to deal with CocoaJava's subtle quirks. For
example the documentation on AutoreleasePools is way thin. When and why
should I use them?
I agree. Real JavaBrigde documentation seems to be missing. Hopefully,
we have a ML :)
-Maurice
--
Julien Dufour