Millennium bug in clock
 

NOT wanting to digress from moving ahead to clams...:nag: but there may be a millennium bug in Jim's clock code. Setting the year back... 1999 or previous garbles up the year shown on the crystal...

Now, see why it's only in the BetaBeta, and not the ReleaseBeta? Good catch.

Edit: OK, I fixed it so that the third digit will display properly. The first two digits are hard-coded to be "20", though, so it can't do 1999.

Oh no! What about all the people running the aquarium in a Windows emulator in the year 3000? ;)

By the way. I just woke up from a really strange dream. Jim visited me but i really dont know why. Must have been some kind of vacation. :eek::loco:

BTW is the date internationalised or does everyone get the non-US version, which would work for me (9 Feb not Feb 9)?

You might be painting yourself into a corner if you are displaying "20" instead of reading the year. Are you reading the day-of-the-week using locale?

Can it do 21?

Nope. I'll have to do an update when I'm 151.

LoL, Just thought: the new "MA8" by J. Sachs VII

I only have one offspring, and she has no interest in computers.

Thanks for the clock:)

I see with this version the millennium bug has changed... the "20" stays while the last 2 digits are correct. You might loose some of the Amish customers that like to see 1899:D

To much programming to hook up those two digits. They will always be "20" for the rest of my lifetime, and many years beyond.