Development vs Standalone
Sarah
sarahr at genesearch.com.au
Sun Nov 24 17:59:01 EST 2002
Is the splash screen the main stack or do you have another stack which
contains all the general handlers but which got bumped down the
hierarchy when you inserted the splash stack? That's what happened to
me once when using the splash screen approach. The solution was to have
an extra line in your splash screen openStack handler:
start using "The stack with all my scripts"
When you do a build like this, my preference is to say "No data folder"
as well as using "Move substacks..."
If you do this, you will find your application folder includes the
clickable app as well as a folder called
"My App.rev_components". I find this works better than creating a data
folder which has this components folder as a sub-folder of it.
Sarah
On Monday, November 25, 2002, at 12:00 pm, Robert Presender wrote:
> Hi,
> I assume that I am doing something wrong. Will appreciate help.
>
> Using OS 10.2.2/rev 1.1.1r2(OSx)/Emac also OS 9.2.2/rev 1.1.1r2(OS)/PB
> G3
>
> My project works OK in the development stage but when I do a Build,
> the standalone doesn't execute properly.
>
> The standalone opens with the Splash, etc but doesn't want to execute
> some custom btns both menu and other types on substacks.
>
> All my substacks appear in the Data folder of the standalone.
>
> It seems that some btn menus don't activate their applicable
> handlers in the Main stack when in Build but do so when in
> development.
>
> Selected build options are as follows:
> Basic .. Create folder for substacks, Mac OSX, auto download.....
>
> Stacks .. Current stack file, copy default font and color, remove Rev
> UI ..., move substacks into indiv files, auto apply stackFiles info to
> mainStack
>
> Resources.. ask,answer,cursors, icon lib
>
> MacOS option .. only creatpr signature.
>
> TIA
> Regards ... Bob
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
More information about the use-livecode
mailing list