Digital Clock Bug / Glitch 5:59 -> 6:00 -> 0:01

[Agonizer]

I've searched the forum but not found a report for this 'bug' so i decided to open a new topic about this. When the EL-Day is over, the digital clock Jumps from 5:59 to 6:00 to 0:01, but (IMHO) it should be 5:59 -> 0:00 -> 0:01

 

I have the linux 1.4.0 beta client if this matters.

 

I've searched bug-reports for 'clock' but not found a matching topic so i started this one. I hope i havn't missed something

[Cycloonx]

It's always been like this iirc. So not a real bug.

[Torg]

*shrug*... I figure it makes sense so a "fix" will be in CVS shortly.

[LabRat]

*shrug*... I figure it makes sense so a "fix" will be in CVS shortly.

I just do % 360 in the line that receives the time from the server

[Torg]

*shrug*... I figure it makes sense so a "fix" will be in CVS shortly.

I just do % 360 in the line that receives the time from the server

Actually, that's a nicer fix than I had... so I'll change my code. I can't update it atm anyway cos CVS isn't responding after logging in... o.O

 

Wait a min... that's already in.

[ttlanhil]

Yes, some of Karen's code had it %=360 in an #ifdefr, and in a recent cleanup I moved it out of the #ifdef.

Realistically, it should be 6:59->1:00, since the idea of zero is actually pretty new; but it's not like realism, believability, or any approach at historical accuracy has much importance here.