Oh, of course! Given that my “main stack” was a livecode stack, I didn’t even
think about that. Thank you for pointing that out.
be well,
randy
Randy Hengst
www.classroomFocusedSoftware.com
> On Mar 8, 2016, at 3:52 PM, J. Landman Gay wrote:
>
> On 3/8/2016 3:00 PM, Randy Hengst wrote:
>> I
On 3/8/2016 3:00 PM, Randy Hengst wrote:
I spoke a bit too soon… the “answer” dialogue still doesn’t show. I
did try “start using stack “launcher.livecode” but no answer
dialogue.
Is the answer dialog checked in standalone settings?
--
Jacqueline Landman Gay | jac...@hyperactivesw.
e launcher and the engine are combined into
>> the executable within MacOS folder within the app's package. The main stack
>> and other resources will also be in that folder, either as is or in any
>> folder structure you have constructed. Isn't that where you want them?
, either as is or in any
> folder structure you have constructed. Isn't that where you want them?
> They should all be in the 'package' else they won't be part of your app.
>
> James
>
>
>
> --
ve constructed. Isn't that where you want them?
They should all be in the 'package' else they won't be part of your app.
James
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Launcher-Stack-and-Saving-tp4702096p4702110.html
Sent from the Rev
You'd think it should work since you followed the lesson exactly. But
try putting the launcher stack in use before you close it. That will
keep its resources available. Closing a stack generally removes it from
the message path.
On 3/7/2016 3:26 PM, Randy Hengst wrote:
Hi All,
I’m working fo
Hi All,
I’m working for the first time with the “launcher” stack process to be able to
save in a livecode stack.
OSX 10.10.5 and LC 7.1.1
I’ve followed this lesson:
How do I save custom properties in a standalone application?
http://lessons.livecode.com/m/4071/l/17375-how-do-i-save-custom-prop
