AW: AW: The Art of Dissolving Splash Screens
Tiemo Hollmann TB
toolbook at kestner.de
Thu Jun 28 03:02:47 CDT 2007
Richard, which message or info do you check for knowing if the boot is
fullfilled without problems? Just sysError and the result?
Von: use-revolution-bounces at lists.runrev.com
[mailto:use-revolution-bounces at lists.runrev.com] Im Auftrag von Richard
Gesendet: Donnerstag, 28. Juni 2007 09:44
An: How to use Revolution
Betreff: Re: AW: The Art of Dissolving Splash Screens
Tiemo Hollmann wrote:
> Just for my interest, what is the advantage of using a separate splash
> instead of using a splash card or splash image/graphic in mainstack? There
> must be some, which I don't see.
There's a million different ways to structure an app in Rev. For
myself, I use the mainstack only to boot the app, and the only UI it has
is an error dialog notifying the user of a problem on boot. Once the
boot is successful I hide that window and move on to the splash, and
eventually the document window or welcome screen, depending on the app.
I do this because if all else fails at boot, the app's mainstack will
become visible and be sitting there in front of the user anyway. So
using it as a boot error dialog allows it to do something meaningful in
the event of a worst-case boot error, and if there is no error then
everything just moves forward as normal.
Managing Editor, revJournal
Rev tips, tutorials and more: http://www.revJournal.com
use-revolution mailing list
use-revolution at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
More information about the use-livecode