Using the ESTK

[_Andrew-Hall_]

This is a genuine question - what do you use it for.

Every potentially useful thing I try to do on it (for example capture variable values mid-script or run scripts from it etc), either does not seem to work or is so difficult to get to work it is easier to debug without it (by putting breaks and alerts in the script itself and running outside the ESTK). I'm sure this is my lack of understanding and skill with the ESTK - could some of you who use it just step through some of the more simple but worthwhile things you do with it.

Andrew

[_Andrew-Hall_]

I'm beginning to get it - a big part of my problem is that I started testing with a bridge script and ESTK has to be 'unfreezed' regularly - I had difficulty establishing if this was something I was doing wrong (which often it was of course). I would still be interested comments on usage.

Andrew

[_Robert_Stucky_]

That freezing is a known bug when trying to work with bridge from estk.

Easiest way to unfreeze is click the bridge window and back to estk. It's a pain, but the debugger is worth it.

Once you are in the debugger, it's pretty much standard fare for debugging. It certainly beats the heck out of alerts and what not.

When attempting to execute a bridge script or command line from the console, you can switch the app drop down list from bridge to estk and back to bridge and the script/line will execute and return.

Don't forget about the $ object.

$.writeln in your bridge code will write to the estk console. That's also much better than alerts.

Bob