And I'll go get it now, since I have a minute, and try it again. I did try an early version, had some issue, and just didn't have the time <so to speak> to keep up with updates etc.
Chip -----Original Message----- From: Vic Beckley [mailto:[email protected]] Sent: Friday, April 05, 2013 8:28 PM To: [email protected] Subject: RE: Timer in apps stop working Bruce, I use your app all the time on all my PCs so you should feel a little better! LOL! Vic -----Original Message----- From: BX [mailto:[email protected]] Sent: Friday, April 05, 2013 8:23 PM To: [email protected] Subject: Re: Timer in apps stop working Hey Chip, What is going on ere? Granted I modified the "Hourly Chime" but give me a break, I spent a long time getting more things into that routine. But, It is nice to know that my app was not used... Sincerely Bruce Sent: Friday, April 05, 2013 8:13 PM Subject: RE: Timer in apps stop working Hi Rod, I have not noticed this, and I use the hourly chime app (written by GW) all the time. Does your clock app happen to use SAPI speech? I am wondering if there's something (not necessarily timers) which you might be using in this app which is really causing the problem, and is unusual enough it wouldn't normally be used, and I thought of using SAPI speech to produce high quality sounding output. Or perhaps you are playing your own .wav files which you recorded yourself (and so maybe they have some quality which can cause the playback routine to hang)? You could try the hourly chime app from GW; it's extremely simple to use, and if it never failed, you might be convinced the problem isn't the use of timers anyway, and the source code to this app is available for you to study and learn from (and the app being simple enough, it's pretty easy to understand). Or on the other hand, if it also fails for you, then maybe something else running on your pc is interfering with timers? Hth, Chip -----Original Message----- From: Rod Hutton [mailto:[email protected]] Sent: Friday, April 05, 2013 2:13 PM To: [email protected]; [email protected] Subject: Timer in apps stop working 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 :)
