Chip 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.
Yes, that would have been great. Something for GW staff, I guess. As far as
I get it, they will have to give us a chance to run the WE object module,
apart from WE itself.
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.
because, regardless of which of these methods you use, it's easy to write
a
script which accidentally disables your entire system by "eating" all
keystrokes.
Hmm?? Tell me, please, why all that hazzle. You can define a Userprofile in
WE, name it Scripting. Long as this is not your default user profile in WE.
WE will always start with the DEFAULT profile as the active one. Your
scripts would be stored in the Window-Eyes\Users\Scripting folder, hence
only be loaded when you switch to that user profile in WE. If something goes
wrong, simply reload WE, and you are back in the default user profile, and
can manully go into the folder and delete, edit or move your offending
Script.
Another benefit hereof, would ber that you could have the scripting profile,
ripped of any other peoples scripts, ensuring that you can test your
scripts, without worrying, that strange behavior, would be caused by certain
confilcts with what others have decided to do in their scripts.
