On Jun 30, 2005, at 10:39 AM, Scott Ellsworth wrote:
Perhaps a good way to investigate this would be to pass the
Headless flag, then see if it gets any further. (Since a screen
saver is not headless, you will need to resolve this eventually,
but it might give good bug report fodder.)
It might also we worth asking the Eclipse folks whether they solved
mixing the AWT and Carbon event loops for Eclipse, and if so, how?
I'm currently working on an SWT application, so I've been following
the Mac integration stuff for SWT (which Eclipse is built on) pretty
closely. The issue has been exactly what you've mentioned: AWT and
SWT fighting for control of the event thread.
The initial fix for this in SWT land was a custom java_swt binary
built to start SWT applications on the first thread, which allowed
SWT to work properly, but prevented any calls to AWT to work correctly.
In the last 1.4.2 Java build, Apple provided the -XstartOnFirstThread
parameter, which allows the standard java binary to be used to run
SWT applications, but which still prevents AWT from being mixed with
SWT applications.
In our application, we use JasperReports, which uses AWT or Swing,
not sure which, but we've had some success recently in getting it to
run with -Djava.awt.headless=true -- I think the JasperReports stuff
uses AWT or Swing to draw images which then get passed to SWT
somehow. Performance is acceptable, although printing is still an
issue on Mac OS X for us, but it's a lot further along than it used
to be.
Hope this helps,
--
Peter Molettiere
Founder, Green Array
_______________________________________________
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
