Does it flash if you unjar the app and launch it from the command line with a splash screen image filename?
I've only played around with this new feature and haven't use the jarred version,
but I haven't seen any flashing.
Do you have any code that manipulates the java.awt.SplashScreen object,
or is that manifest entry the extent of your splash screen involvement?
> what is the advantage of the native splash over
> making one yourself?
The spash screen comes up before the JVM and as the app is loading.
I guess its just there to pacify people who think the JVM and App Startup
is too slow. I know people at my job have actually said to me when
running a Java app "why does it load sooo much slower than a VB
app?" when in actuality it came up in an eye blink.
I guess VB apps load in half an eye blink, lol.
> Do you have any code that manipulates the java.awt.SplashScreen
I thought that because the SS comes up before the JVM (or concurrently
or whatever) that you couldnt control it?
http://java.sun.com/developer/technicalArticles/J2SE/Desktop/javase6/splashscreen/
"Java 6, provides a solution that allows the application to show the splash screen much earlier, even before the virtual machine starts."
As for why:
"Before [a java programmed AWT] splash screen can pop up, the application has to load and initialize the JVM*, AWT, usually Swing, and perhaps some application-dependent libraries. The resulting delay of several seconds has made use of a Java technology-based splash screen less than desirable."
>> Do you have any code that manipulates the java.awt.SplashScreen
>
> I thought that because the SS comes up before the JVM (or concurrently
> or whatever) that you couldnt control it?
What happens is that the Image comes up first and then your code that
manipulates the image starts a moment later. For example, you may
be doing a little animation, or writing on a clear spot on the image.
So you definitely can combine splash screen code with an initial image.