Build-time v Run-time

Robert Sneidar slylabs13 at me.com
Fri Feb 15 13:20:41 EST 2013


Easy enough to just click the suppress messages button before opening the stack. You will probably want to keep messages suppressed in this situation if going to other stacks and cards is going to trigger actions that the openstack has not set up yet. You can make a handler called startApp or something similar that the preOpenStack handler traps, so you can call it at will when you need to do runtime testing. 

Bob


On Feb 15, 2013, at 9:23 AM, Robert Brenstein wrote:

> On 15.02.2013 at 17:56 Uhr +0100 Graham Samuel apparently wrote:
>> Another naive questions, but this hasn't happened to me before, or at least I haven't recognised it properly.
>> 
>> I'm looking at some code written by an associate. As normal (to me) it's a mainstack and a lot of substacks. I want to tinker with the code, so I open the mainstack in the LC IDE, and immediately the program starts to run, even though the Edit tool is active in the toolbar rather than the Browse tool - it starts up and does stuff, like the IDE does. I don't want that, I want the code to remain entirely passive until I tell it to run!
>> 
>> How does a stack get into 'instant run mode' like that, and what can I do to stop it? Is there some way of creeping up on it so that no handler is executed?
>> 
> 
> Apparently, your associate coded something in one of the openXxxx handlers to start execution. Those handlers run regardless of the IDE mode. To achieve what you want, the code should check the environment (look it up in the dictionary) and do not execute if it is "development". If you want to be able to execute after all, to simulate standalone execution, you may add checking whether the alt key is down, and if it is down, execute regardless of the environment.
> 
> Robert
> 
> _______________________________________________
> use-livecode mailing list
> 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