AW: AW: The Art of Dissolving Splash Screens
ambassador at fourthworld.com
Thu Jun 28 17:51:27 CDT 2007
> Richard wrote:
>> 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
> Richard, which message or info do you check for knowing if the boot is
> fullfilled without problems? Just sysError and the result?
Not even that. I assume the worst-case scenario: too little memory to
do ANYTHING (rare since the death of OS 9, but possible), in which case
even sysError would fail.
So the error window which is my app's mainstack has only hard-wired text
with a very generic message:
This application was unable to launch successfully, possibly
because of a low-memory error or missing component.
Please re-install and try again.
If the problem persists please contact technical support
It's not very informative, but thankfully as far as I know no one's had
to see it in more than five years since shortly after I started using
it. Once the app has initialized its libraries any other error
reporting can use things like the err handler noted in a previous post,
providing a more informative report to the user with specific
recommendations for remedy.
Managing Editor, revJournal
Rev tips, tutorials and more: http://www.revJournal.com
More information about the use-livecode