I managed to read most of the eclipse's bug 67384 thread. So if I am
not summarizing this correctly, let me know:
1) OS X requires that the UI event thread lives in thread #0.
2) SWT, for all practical purposes in OS X, renders the AWT event
handlers useless. Currently, there is no way to make the AWT event
handler thread and the SWT's work in the same process.
3) Since eclipse is a SWT application, any eclipse plug-in that wants
to use AWT/Swing needs to use it in another process.
So a valid work-around to this problem, if the performance penalty is
acceptable, would be to delegate the AWT/Swing code to a second
process that does not involve SWT/eclipse at all, no?
If I were to use java.lang.Process or something equivalent this should
suffice to have the swt event handler in thread #0 and the AWT event
handler in thread #0 also.
Am I too off base here?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
