Re: Launcher Stack and Saving

[Randy Hengst]

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 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.com
> HyperActive Software   | http://www.hyperactivesw.com
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Launcher Stack and Saving

[J. Landman Gay]

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.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Launcher Stack and Saving

[Randy Hengst]

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.

Any thoughts on what I have missed?

be well,
randy

Randy Hengst
www.classroomFocusedSoftware.com


> On Mar 8, 2016, at 2:17 PM, Randy Hengst <iowahen...@mac.com> wrote:
> 
> Jacque and James,
> 
> Thank you for the tips… yes, I do want the main stack to be in the package… I 
> placed it in the same folder simply because of the instructions in the lesson 
> I referenced… when I first tried to include the main stack, I didn’t select 
> “resources” as the destination folder… all is good on that front now.
> 
> And, yes, the shutdownrequest message what I was missing.
> 
> Thank you both for helping move forward.
> 
> be well,
> randy
> 
> Randy Hengst
> www.classroomFocusedSoftware.com
> 
> 
>> On Mar 8, 2016, at 7:41 AM, jameshale <ja...@thehales.id.au> wrote:
>> 
>> Randy Hengst wrote
>>> Second, when I “quit” the launcher the changes made to the “main” stack
>>> are not saved. However, when I close by clicking the “red” dot of the
>>> “main” stack, the changes are saved. 
>> 
>> I have not gone through the lesson but the launcher/mainstack structure
>> usually implies that once the "launcher" has done its bit, the "main" stack
>> is the one left open. Thus to quit, you are quitting the main stack, not the
>> launcher. If this is the case then the "closestack" message sitting in your
>> main stack is only sent when the user or a handler "closes" its window. Is
>> this what you are doing to "quit". 
>> If not, perhaps you want to act on the "shutdownrequest" message
>> (remembering to pass it)?
>> 
>> 
>>> Finally, is it possible to place the “main” stack in the OSX package
>>> rather than having the stack in the same folder as the launcher
>>> standalone?
>> 
>> When you build the standalone the 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? 
>> 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 Revolution - User mailing list archive at Nabble.com.
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Launcher Stack and Saving

[Randy Hengst]

Jacque and James,

Thank you for the tips… yes, I do want the main stack to be in the package… I 
placed it in the same folder simply because of the instructions in the lesson I 
referenced… when I first tried to include the main stack, I didn’t select 
“resources” as the destination folder… all is good on that front now.

And, yes, the shutdownrequest message what I was missing.

Thank you both for helping move forward.

be well,
randy

Randy Hengst
www.classroomFocusedSoftware.com


> On Mar 8, 2016, at 7:41 AM, jameshale <ja...@thehales.id.au> wrote:
> 
> Randy Hengst wrote
>> Second, when I “quit” the launcher the changes made to the “main” stack
>> are not saved. However, when I close by clicking the “red” dot of the
>> “main” stack, the changes are saved. 
> 
> I have not gone through the lesson but the launcher/mainstack structure
> usually implies that once the "launcher" has done its bit, the "main" stack
> is the one left open. Thus to quit, you are quitting the main stack, not the
> launcher. If this is the case then the "closestack" message sitting in your
> main stack is only sent when the user or a handler "closes" its window. Is
> this what you are doing to "quit". 
> If not, perhaps you want to act on the "shutdownrequest" message
> (remembering to pass it)?
> 
> 
>> Finally, is it possible to place the “main” stack in the OSX package
>> rather than having the stack in the same folder as the launcher
>> standalone?
> 
> When you build the standalone the 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? 
> 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 Revolution - User mailing list archive at Nabble.com.
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Launcher Stack and Saving

[jameshale]

Randy Hengst wrote
> Second, when I “quit” the launcher the changes made to the “main” stack
> are not saved. However, when I close by clicking the “red” dot of the
> “main” stack, the changes are saved. 

I have not gone through the lesson but the launcher/mainstack structure
usually implies that once the "launcher" has done its bit, the "main" stack
is the one left open. Thus to quit, you are quitting the main stack, not the
launcher. If this is the case then the "closestack" message sitting in your
main stack is only sent when the user or a handler "closes" its window. Is
this what you are doing to "quit". 
If not, perhaps you want to act on the "shutdownrequest" message
(remembering to pass it)?


> Finally, is it possible to place the “main” stack in the OSX package
> rather than having the stack in the same folder as the launcher
> standalone?

When you build the standalone the 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? 
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 Revolution - User mailing list archive at Nabble.com.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Launcher Stack and Saving

[J. Landman Gay]

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 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-properties-in-a-standalone-application

And have created a “launch” stack and “main” stack as outlined. So, this code 
is in the launcher:
on openStack
 open stack "Main Application.livecode"
 close stack "Launcher"
end openStack

And, in the main stack I have this code
on closeStack
save this stack
pass closeStack
end closeStack

The “main” stack opens just fine…  But, I’ve run into a couple bumps for which 
I haven’t found an answer in the lists or forum.

First, my “answer” calls don’t work when I open the “main” stack from the 
launcher. They work just fine in the IDE. Nothing appears at all. The script 
does run as if the “answer” call isn’t there… no error, etc.

Second, when I “quit” the launcher the changes made to the “main” stack are not 
saved. However, when I close by clicking the “red” dot of the “main” stack, the 
changes are saved.

Finally, is it possible to place the “main” stack in the OSX package rather 
than having the stack in the same folder as the launcher standalone?

be well,
randy

Randy Hengst
www.classroomFocusedSoftware.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Launcher Stack and Saving

[Randy Hengst]

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-properties-in-a-standalone-application

And have created a “launch” stack and “main” stack as outlined. So, this code 
is in the launcher:
on openStack
open stack "Main Application.livecode"
close stack "Launcher"
end openStack

And, in the main stack I have this code
on closeStack
   save this stack
   pass closeStack
end closeStack

The “main” stack opens just fine…  But, I’ve run into a couple bumps for which 
I haven’t found an answer in the lists or forum.

First, my “answer” calls don’t work when I open the “main” stack from the 
launcher. They work just fine in the IDE. Nothing appears at all. The script 
does run as if the “answer” call isn’t there… no error, etc.

Second, when I “quit” the launcher the changes made to the “main” stack are not 
saved. However, when I close by clicking the “red” dot of the “main” stack, the 
changes are saved. 

Finally, is it possible to place the “main” stack in the OSX package rather 
than having the stack in the same folder as the launcher standalone?

be well,
randy

Randy Hengst
www.classroomFocusedSoftware.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode