Open Stack, LC exits
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
Open Stack, LC exits
I am trying to open my stack. I hve clicked on Edit mode first to make sure I'm in edit mode.
I open the stack, then LC closes.
I do have a quit in my "on openstack" at the end, but I'm not sure if somehow that's causing the issue.
I open the stack, then LC closes.
I do have a quit in my "on openstack" at the end, but I'm not sure if somehow that's causing the issue.
Re: Open Stack, LC exits
HI asawyer13,
1. You can use the message box: lock messages; go stack "the/one/that/quits.livecode"
OR
2. Select menu: "Development" -> "Suspend Development Tools"
Whcich does basically the same, but you need to click "Restore Development Tools" later after opening your "quitting" stack.
Best
Klaus
well, what if not this?asawyer13 wrote:I am trying to open my stack. I hve clicked on Edit mode first to make sure I'm in edit mode.
I open the stack, then LC closes.
I do have a quit in my "on openstack" at the end, but I'm not sure if somehow that's causing the issue.
1. You can use the message box: lock messages; go stack "the/one/that/quits.livecode"
OR
2. Select menu: "Development" -> "Suspend Development Tools"
Whcich does basically the same, but you need to click "Restore Development Tools" later after opening your "quitting" stack.
Best
Klaus
Re: Open Stack, LC exits
I tried the Suspend Development Tools because I thought I saw that on another post, however once I do that, LC is gone except for the message box that says "restore development tools", so I can't actually open the stack????
Re: Open Stack, LC exits
But the first method you suggested, worked.
Is there a more proper way to have a quit in the stack but not have it cause a problem?
Is there a more proper way to have a quit in the stack but not have it cause a problem?
Re: Open Stack, LC exits
Well, QUIT means QUIT! No way to change this fact
You could add this to our script so you can open and edit the stack in the LC IDE:
Best
Klaus
You could add this to our script so you can open and edit the stack in the LC IDE:
Code: Select all
...
if the environment <> "development" then
quit
end if
...
Best
Klaus
Re: Open Stack, LC exits
Klaus
I understand what you are saying, but most programming languages when you actually open the program to make changes, it doesn't actually run the program....
LC is new to me, but I will understand it's nuances eventually. Thanks for your help.
Alan
I understand what you are saying, but most programming languages when you actually open the program to make changes, it doesn't actually run the program....
LC is new to me, but I will understand it's nuances eventually. Thanks for your help.
Alan
-
- VIP Livecode Opensource Backer
- Posts: 3581
- Joined: Mon Jan 22, 2007 7:36 am
- Location: Berkeley, CA, US
- Contact:
Re: Open Stack, LC exits
Alan- why do you want your stack to quit as soon as it opens? That's what you're telling it to do.
PowerDebug http://powerdebug.ahsoftware.net
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
Re: Open Stack, LC exits
Hi Mark,
Best
Klaus
check this: http://forums.runrev.com/phpBB2/viewtop ... =7&t=15443mwieder wrote:Alan- why do you want your stack to quit as soon as it opens? That's what you're telling it to do.
Best
Klaus
-
- Livecode Opensource Backer
- Posts: 328
- Joined: Mon Dec 05, 2011 5:34 pm
- Location: Thailand
- Contact:
Re: Open Stack, LC exits
Hi Alan,
Can't agree with you more about the weirdness of having a program run as soon as you try to edit it - it's utterly silly in so many ways! But, as you and I are the only 2 people in the whole LC community who seem to see this craziness, we have to put up with it.
Things you will have to get used to:
Save often! I mean more than usual in an IDE. There are things that you can type that might cause the whole thing to lock up/crash at the least expected time.
Backup your .livecode file often! Once you have something you are happy with then make a copy of the file - just to be on the safe side.
Be vary careful with automatic sending of messages when you are editing. If you half change some code in something that is going to be called in the background then switch off Messages (int the tool bar) before you 'Apply' the code. Then Save.
Wear a Wig. The IDE WILL lock up at some point. The wig will help you retain some of your hair - unless you are already bald, of course!
Save your file again. It really doesn't cost much to save the file again. Do it before you hit that Run (browse) button - Always!
There is more - but I will leave you to discover them. That's why the Wig is a good idea!!
Once you get into the routines then the actual programming with LC becomes quite pleasant and productive. Almost enjoyable!
Cheers,
Dave
Can't agree with you more about the weirdness of having a program run as soon as you try to edit it - it's utterly silly in so many ways! But, as you and I are the only 2 people in the whole LC community who seem to see this craziness, we have to put up with it.
Things you will have to get used to:
Save often! I mean more than usual in an IDE. There are things that you can type that might cause the whole thing to lock up/crash at the least expected time.
Backup your .livecode file often! Once you have something you are happy with then make a copy of the file - just to be on the safe side.
Be vary careful with automatic sending of messages when you are editing. If you half change some code in something that is going to be called in the background then switch off Messages (int the tool bar) before you 'Apply' the code. Then Save.
Wear a Wig. The IDE WILL lock up at some point. The wig will help you retain some of your hair - unless you are already bald, of course!
Save your file again. It really doesn't cost much to save the file again. Do it before you hit that Run (browse) button - Always!
There is more - but I will leave you to discover them. That's why the Wig is a good idea!!
Once you get into the routines then the actual programming with LC becomes quite pleasant and productive. Almost enjoyable!
Cheers,
Dave
Coding in the Sun - So much Fun.
Visit http://electronic-apps.info for released App information.
Visit http://electronic-apps.info for released App information.
-
- VIP Livecode Opensource Backer
- Posts: 3581
- Joined: Mon Jan 22, 2007 7:36 am
- Location: Berkeley, CA, US
- Contact:
Re: Open Stack, LC exits
Klaus- thanks for the context. That does make sense now.
PowerDebug http://powerdebug.ahsoftware.net
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
PowerTools http://www.ahsoftware.net/PowerTools/PowerTools.irev
Re: Open Stack, LC exits
Hi Dave,
Best
Klaus
you definitively made my day!Wear a Wig. The IDE WILL lock up at some point. The wig will help you retain some of your hair - unless you are already bald, of course!
Best
Klaus
Re: Open Stack, LC exits
I'm pretty much bald so a wig is my only hope.
lol
lol
-
- VIP Livecode Opensource Backer
- Posts: 7214
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: Open Stack, LC exits
Not needing to compile before running is actually promoted as a feature of LiveCode. It does take a little getting used to if you're coming from more traditional languages, but it's easy to click the Messages button before opening a stack if that's the behavior you want. You can have your cake and eat it too.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: Open Stack, LC exits
Now that I understand how it works, I think it will be fine.
I did also have to stop hiding the stack when I was in development also..
It's kind of crazy, but I can deal with it.
I did also have to stop hiding the stack when I was in development also..
It's kind of crazy, but I can deal with it.
-
- VIP Livecode Opensource Backer
- Posts: 9802
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: Open Stack, LC exits
You mean LiveCode is live code? How was I supposed to know?jacque wrote:Not needing to compile before running is actually promoted as a feature of LiveCode. It does take a little getting used to if you're coming from more traditional languages, but it's easy to click the Messages button before opening a stack if that's the behavior you want. You can have your cake and eat it too.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn