Standalone Build Problem

Bob Sneidar bobsneidar at iotecdigital.com
Tue Jun 2 18:35:43 CEST 2015


Thanks Devin.

With this approach I am finding that letting Livecode automatically find the libraries it needs is not successful. First, none of my data grids work, even though I have added a data grid to the splash stack. Second, none of the image files I have referenced in the primary stack are being accessed. I suppose I will need to manually add those as well to the application folder.

I will, at the risk of sounding like I am whining, repeat the sentiment others have expressed, that this is more difficult to get working than it ought to be.

Bob S


On Jun 2, 2015, at 09:21 , Devin Asay <devin_asay at byu.edu<mailto:devin_asay at byu.edu>> wrote:


On Jun 2, 2015, at 10:09 AM, Bob Sneidar <bobsneidar at iotecdigital.com<mailto:bobsneidar at iotecdigital.com>> wrote:

Hi all.

So I am creating a standalone for the first time, and I am trying to use a splash stack. Taking the advice of others I have added a data grid to the splash stack so that the data grid library get added. Now when I attempt to set the mainstack of the actual stack that contains all the business logic, it fails. I think I might know why, but I’ll ask to be sure.

The actual application stack has a number of substacks already. I am thinking that a substack cannot itself contain other substacks. If this is true, I will have to break out all of my other stacks as single files, then add them as substacks to the mainstack.

If this is true, I can see why new users have problems creating standalones at first. It is a rather convoluted way of going about things. If not, then I am at a loss to know why I cannot set the mainstack property of a given stack.

I have also tried using the message box:
set the mainStack of stack "Forms Generator" to "Forms Generator Splash”

I get:
Script compile error:
Error description:

Bob,

Don’t try to make your mainstack (the stack with your business logic) a substack of the splash stack. They should both be mainstacks, and the splash stack (now app) should simply “go to” the other stack. Looking at it another way, the splash stack is simply built into an application that contains the engine, which in turn can launch any other stack you want.

HTH

Devin

Devin Asay
Office of Digital Humanities
Brigham Young University


_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com>
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



More information about the use-livecode mailing list