I'll guess that's the best that the built-in splash screen mechanism can do
(though I haven't researched it.) I've always used my own system so I can
start it up and close it down when I want and how I want.
I'll make a suggestion though. The VB6 method you are referring to is
(probably) no better if by that you mean estimating that after (n) seconds
the system has probably initialized. Rather than set a timer for say 5
seconds (at which time the splash screen is gone) I set it up with a bit
more code so that 5 seconds is the "minimum" time. If initialization is
short (like yours) then it determines it has 4 more seconds to go, if it
takes 6 seconds to get started it determines that the 5 seconds needed has
elapsed and the splash screen can close. You never close the screen early
and you are guaranteed it appears for a minimum amount of time to read it.
As for Herfried's reply. Yes in a way you do want to delay the user even if
the app is ready. First it is simply annoying to blink a screen but more
importantly displaying the splash screen at all can be made a user-selected
option. So the options are a reasonable splash screen effect or no splash
screen effect but never an annoying splash screen effect :-)
"will_456" <wi;ll****@bigpond.comwrote in message
news:uV*************@news-server.bigpond.net.au...
In vb2005 Express:
In My Project Application Splash Screen I have selected my splash
screen form.
The form opens on project startup but closes immediately before anyone
would have time to read it. I presume it only stays visible while the main
form initialises.
This is not long enough but I can't see how to slow it down.
Should I set the splash screen using the Application settings or go back
to opening it from the main form and then close it with a timer (old vb6
common method).