Using a little scripting magic, I<code> Go can use DroidScripts native error routines as if you were connected to the PC IDE.

If an error occurs you will get the error message, the line number, and the file opened in the editor. The cursor will be placed on the error line.


What must I do?

Nothing different than you have been. This will all take place transparently with I<code> Go injecting the error routines into your app.

I don't want extra code in my app!!

There never will be! After you return to I<code> Go the code will be immediately removed and you will never see the snippet needed to make this handling of errors possible.

It didn't return to I<code> Go, now what?

Don't worry! Most Android devices have enough memory to handle our editor and DroidScript in memory together, and upon completion of your app, or if an error occurs, I<code> Go will automatically reopen. If it doesn't --- simply open I<code> Go from your homescreen and the process will continue uninterrupted.


Some considerations...

Use app.LoadScript( ... ) when including JavaScript files into your app. This makes sure if an error occurs you will know which file the error occurred in.

It is important if you are using any other outside editors, including the PC IDE, that you complete a run cycle (Run project from the Tools Menu - reopen I<code> Go when done). This insures the error snippet is properly removed and not in your code. Even if this cycle is interrupted --- opening the editor will complete the cycle.

A note about HTML apps...

You must be sure this line...

<script src='file:///android_asset/app.js'I>I</script>

... is within the <head> section of your app and prior to any code you may add to your app. If you use a New Project template here or a DroidScript New HTML app this line will be included as is. Please take note of the single quotations.


Enjoy debug and error information when you are away from your PC and the DroidScript IDE.