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.
(Any reply from me on this thread is suspect, but...)
I suspect integrating anything beyond a toy integration of Swing
components into SWT is going to run into pretty serious trouble; bear
in mind that the threading code for most multithreaded Swing apps lives
and dies by SwingUtilities.isEventDispatchThread() and
SwingUtilities.invokeLater(); it's provably dangerous to access (or
even construct) Swing components from other threads than the event
dispatch thread (with a minor exception if the app has yet to display
any GUI at all). The odds of keeping two guis with their own distinct
event loops sandboxed so well that code from one toolkit's event thread
never enters the other toolkit's components' methods except on the
other toolkit's event thread are pretty slim unless the code was
written from the ground up with that in mind. Without that, well, you
get something that looks like it works, and even probably does work a
good deal of the time - but not really something you want to use in
production code.
-Tim
_______________________________________________
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
