[continued from previous message]

local display to fix it.

This adjust the broadcast time based on the TZ you have selected.
I.e., it wouldn't work in europe. Or AK/HI! etc.

I have an analog electro-mechanical (hands on dial) "atomic" clock
that does this. Position the hands so they reflect the current local
time and push a button on the mechanism. From that point the time
broadcast keeps it correct [at least until the batteries die].

This just waits until it acquires signal. Then, sets itself to
the broadcast time, offset by the specified TZ.

I would never have noticed it as it's only role is as a bedside clock.
So, only consulted when I'm thinking about getting up.

If it's "light" -- or "dark"! -- then getting up is just a decision
made based on my own personal preference.

OTOH, if it is dusk/dawn, then I have to think about whether or not
there are any commitments that I have to meet. Evening walk. Morning
shopping trip. Doctor appointment later that day. etc.

In this case, I'd gone to bed in the late afternoon. When I awoke,
the clock suggested it was early morning -- just after sunup.
(Ahhh... a nice long sleep!)

But, C observed: "Well, that wasn't a very long nap..." I.e., it
was *still* early evening, not dawn! :< The "low light" condition
I'd observed was the sun waning, not waxing. (I can't see where the
sun is located in the sky from my bedroom)

----

Now, back to my error/exception problem. I have to see if there are
any downsides to offering a dual API to address each developer's
"style"...

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)