Chip Orange wrote:
keep in mind though, as far as I understand it, in order to test a script
with window eyes you have to add it to the list in the script manager and it
is automatically enabled. a real problem I've had is that if you write a
script which crashes window eyes, each time you start window eyes up again,
your script is there automatically running, and crashing it again. I really
wish we had a way of running ascript, but only once, without adding it to
the list of scripts to be run.
Try running it from immed, using the StartScript method of the
Application object:
StartScript "my_test_script.vbs"
Alternatively, if you want something fully automated, you can write a
short script that defines a hotkey to start the script you're
developing. You could even go a step further and make it fully
configurable as to which hotkeys start which scripts.
so, I strongly suggest a shortcut which starts window eyes manually, using
the commandline parameter which says for it to start without scripting
enabled. and then I suggest you change your window eyes so it does not
start up automatically.
This probably is a good idea. You should also be able to hold down the
shift key while Window-Eyes is starting; that should set the scripting
status to Manual Start.
