From:

 David <trailerdavid@hotmail.com>

Subject:

 Re: a cuckoo clock suggestion

Date:

 Wed, Apr 17, 2013 2:01:27 am

Add on to that, let there be a choice. When wakening the computer (or it
could even be when the app starts for that matter), perform the check Chip
suggested. But let there be a choice for the user, if he wants the time
announced. Now, if he has set it to "no announce on wakeup", then do
nothing. If he has set it to time announcement on the wakeup, then let the
current (correct) time be announced, not the past interval.

So, following up on Chip's example, wakening the computer at 8:30, would
announce 8:30, no matter if the interval was set to only whole hours. After
that, go back to the interval announcement as the user has defined.

Hope all that made sense. At least, this is what I miss in the Hourly Chime
app. My guess is, that you Bruce, simply just copied what was from the
Hourly Chime, and made your add-ons and adjustments. So, the routine for the
interval announcement might just need an update. Smile.


----- Original Message -----
From: "Chip Orange" <lists3717@comcast.net>
To: <gw-scripting@gwmicro.com>
Sent: Wednesday, April 17, 2013 3:11 AM
Subject: a cuckoo clock suggestion


> Hi Bruce,
>
>
>
> Just wanted to mention that I've recently switched from hourly chime to
> your
> cuckoo clock program. I have a laptop, and I have the program set just to
> give me a time announcement upon the hour.
>
>
>
> What I'm finding is that if I put the laptop into sleep mode by closing
> the
> lid (say at 7:30), and then I open it up at say 8:30, I'll hear the
> announcement for the "time is 8 o'clock" as soon as I open the lid.
>
>
>
> I think this is caused by the hourly timer firing then when I open up the
> lid; what I want to suggest is that in your routine which is called when
> the
> timer fires, you might check to see if the time is really what you are
> about
> to announce; if it is not (as in my case), then do nothing.
>
>
>
> Thanks.
>
>
>
> Chip
>
>
>
>