I have a Carbon application here that embedds a JVM. Everything works
fine until I want to start the AWT. As soon as I use JNI to call
Toolkit.getToolkit(), the application hangs and must be forced to
quit.
My guess is that - since I cannot control which thread calls the code
that does Toolkit.getToolkit() (my code is a plugin) - another thread
than the main thread calls my native code and thus
Toolkit.getToolkit() triggers loading the AWT and that blocks
everything.
What do you think, does this sound reasonable?
And, is there a Carbon alternative for Cocoas
"PerformSelectorOnMainThread" that I could use to solve my problem?
daniel.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
