The delays are vital.
you also should to build "spin loops" that wait for windows to appear.
Don't give up on the product.
It is very powerful, but you need to learn to avoid certain things.
And, to religiously USE certain things.
Use KEYSTROKES rather than MOUSE CLICKs if you can.
Use RELATIVE to WINDOW rather than screen (I think the default should be changed).
Pass and store variables in TEXT FILES - it is very fast to read and write files, and the file values can help you debug.
Learn to turn of the "delay" radio button in the editor.
It will make the code much easier to read, but DO keep the delays in between "action" lines.
I use a VARIABLE delays so that I can WATCH the results run (set to 1500 ms) - then I change it to 50 when I am done debugging.
Log to an OPEN notepad so that you can see where you are in the code WITHOUT running the debugger. the debugger is - a little buggy.
So if you are getting inconsistent results, turn off the debugger - or better yet run without the editor being open.
Save often.
Copy entire folders like
MY TASKS
to archive folders like
20008 06 02 at 15:32 my tasks
It is easy to screw things up.
Unfortunately, the syntax doesn't allow you to change code to a comment by just inserting a Quote or a <! - so save often.
Stick with it.
Phil  |