[kepler-dev] Splash screen and corresponding changes
kruland at ku.edu
Tue Feb 14 17:52:16 PST 2006
I've certainly seen many poorly written ui's with redraw bugs. Without
the source code, we can only rely on the documentation. It is rather
unfortunate that Sun recommends creating the entire UI in the event
handler thread (note the big red footnote in
a requirement completely eliminates the possibility of doing things like
a splash screen. I do hope that they cleaned this up for Mustang since
they are releasing splash code in that release.
BTW - after I removed invokeLater completely from
VergilApplication.main() the application rendered all three initial
windows (splash, empty graph tableau, and welcome html) flawlessly.
Perhaps the issues you've had were with previous releases of awt/swing.
Edward A. Lee wrote:
> At 09:13 AM 2/14/2006, Kevin Ruland wrote:
>> However, separate thread can construct new Swing components, but
>> once they are displayed all interaction with the component - through
>> display, keyboard or mouse events - must be through the event handler.
> I don't think this is true...
> I have seen rendering artifacts when swing components are
> constructed in other threads...
> Edward A. Lee
> Professor, Chair of the EE Division, Associate Chair of EECS
> 231 Cory Hall, UC Berkeley, Berkeley, CA 94720
> phone: 510-642-0253 or 510-642-0455, fax: 510-642-2845
> eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal
More information about the Kepler-dev