Hi everyone,

I'm writing to everyone because I'd like some input into the tendency of apps which have timers to stop working when there's some error in the Window-Eyes scripting environment.

Last night, my app which speaks the time every 15 minutes stop working because a pop-up on my system grabbed focus and stopped speech. When I closed the pop-up, which is simply a request to update software, sppeech return, and so I thought everything was okay. However, even though my clock app was still running, the time never announced again, and so I needed to restart it. I have experienced this very often, first, when Window-Eyes speech gets locked up for a brief period of time, or, sometimes (not always, though) when a Window-Eyes app (not a app with a timer) causes an error to occur. My opinion is that any errors or interruptions in the Window-Eyes speech or script-engine environment cause instability which have adverse effects on timer-based functions.

I would appreciate any feedback, if anyone has any, or, at least, I wanted to let people know about this. :)

Take care,

Rod :)

Reply via email to