How does LiveCode decide what stack to build?
Sometimes when I choose "Save as Standalone application" it will build one of the other stacks in my project rather than the main stack.
How/why does it decide to do this?
When I choose to build the standalone, the main card is open, the main stack script is open, and I haven't changed any of the Standalone Application Settings.
How does LiveCode decide which stack to build?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
-
dunbarx
- VIP Livecode Opensource Backer
- Posts: 9648
- Joined: Wed May 06, 2009 2:28 pm
- Location: New York, NY
Re: How does LiveCode decide which stack to build?
I build a couple of standalones. I do not understand your question, though.
In the standalone settings "General" pane, the standalone name is entered. Then in the "Stacks" pane, the stack which is to be the executable is entered. This would be the "splash" stack if you are going that way. I always do.
Below that stack, one may then add other stack files as required. So a standalone is constructed in the above order. What exactly do you mean by "...what stack to build"?
Craig
In the standalone settings "General" pane, the standalone name is entered. Then in the "Stacks" pane, the stack which is to be the executable is entered. This would be the "splash" stack if you are going that way. I always do.
Below that stack, one may then add other stack files as required. So a standalone is constructed in the above order. What exactly do you mean by "...what stack to build"?
Craig
Re: How does LiveCode decide which stack to build?
I guess this is just like selecting "Save" from the file menu,
LC will then take the TOP- or DEFAULTStack and uses that one.
LC will then take the TOP- or DEFAULTStack and uses that one.