On 29-May-04, at 10:57 AM, GAmoore at aol dot com wrote:
Thanks for the detailed suggestion. Actually, one reason for the splash
screen is that the first thing the app does is open several files and
read in
database tables - which takes 10 seconds or so. I am still not 100%
sure if opening
the splash screen (with timer for 3.5 seconds) allows that process to
get
started in the background, so the user has something to view while
that loading
goes on behind the scenes, or if the loading is delayed until after
the splash
closes, but at least it makes the app seem to respond a little faster
because
the splash appears fast.
As for commercial apps, I think of Photoshop, Illustrator, Excel, and
Logic
Pro which all have splash screens - in fact, they often have text
showing which
module is loading which goes by extremely fast.
Yes. But do they use showmodal? This stops the execution of code in the
open event until the window is hidden or closed. This fact should imply
that the splash screen should not be closed until the loading of other
startup files has been completed. In that case, a timer is not required
as you would do it at the end of the open event. You can even update
the screen to show what's loading during the open event like the above
apps you mentioned. In this case you would simply show the window.
Terry Ford
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|