IDE Debug Control: How can I run the whole Program from scra

[Havanna]

I have a largish project in the IDE
Some computations are done on preopenstack,
some more in openstack
and then several things in different cards.

All of it works nicely, but i have not yet found a way to run the whole thing in the IDE from the start.
all the handlers are accessible separately, that's okay.
But sometimes when changes are made in preopenstack or openstack, I have to close remove the project from memory, and then reload it, to get a full run. That of course closes all editors.

Is there a direct way that I have overlooked?

[Klaus]

Hi Havanna,

not a direct way, but almost!

With your stack open, enter this in the MESSAGE BOX and hit ENTER:
send "preopenstack" to stack "your stack name here"
Resp.:
send "openstack" to stack "your stack name here"

You get the picture


Best

Klaus

[Havanna]

thx, Klaus!
That is a good start, though it runs just the respective handler.
What I was looking for is something like a full init, so the application runs thorugh all the phases, just like I freshly open it. Or like the standalone.
Sorry, seems difficult to describe.

[Klaus]

Hi Havanna,

yes, I know what you mean, but that is not directly possible.
This may be one of the few disadvantages of a compile-free programming environment


Best

Klaus

[Havanna]

Hi Klaus,

thx again.
I'm not complaining about not compiling anyway

[jacque]

Sometimes I write a test handler that executes all the commands in order:

Code: Select all

on test 
  preOpenStack
  preOpenCard
 - -  etc
emd test

Then from the message box just call "test".

[dave.kilroy]

For some projects I have a drop-down menu that is only accessible in the IDE via ctrl+click as well as a small 'testing' label which harvests responses from several handlers so I can see what is going on...

[MaxV]

Probably you already know, but for debbugging there are several tools in the Livecode IDE:

• breakpoints
• conditional breakpoints
• variable watch breakpoints
• conditional variable watch breakpoints
• entry messages
• variable check during executing
• variable altering during executing
• show context of use of handlers