Old bug still in Rev 2.8 :( Chapter 3

[Mark Smith]

Joe, I believe the startup handler is only sent to a stack when it's  
the mainstack in a standalone. I could be wrong about this, but it  
seems to be borne out by my experience (and yours, from the sound of  
it).

My solution is to have startup call an "initApp" handler that does  
initialising stuff:

on startup
   initApp
end startup

and then in the card script of card 1 of the mainstack:

on openCard
   if the environment is "Development" then initApp
   pass openCard
end openCard

There may well be better ways to handle this, but it works OK for me.

Best,

Mark


On 21 Feb 2007, at 01:49, LunchnMeets at aol.com wrote:

> Chapter 3
>
> Well, guess what I checked get info on the stack I’d like to open  
> Revolution
> with and it’s set correctly at Rev 2.8 and it’s still not seeing  
> the startup
> handler unless I open that stack from within Revolution. Anyone  
> else want to
> hazard a guess at how to start from a stack and have the startup  
> handler read?
>
> Joe
>
>
> **************************************
>  Check out free AOL at
> http://free.aol.com/thenewaol/index.adp.  Most comprehensive set of  
> free safety and
> security tools, millions of free high-quality videos from across  
> the web, free AOL
> Mail and much more.
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution