I think this is just an aliasing artifact. When seconds are not displayed, gworldclock only updates once per minute. There are no rules on which part of that minute it will update in, it will depend on when you launch the program. Try timing it to launch right at the stroke of the minute hand and you should see gworldclock and date displaying the "same" time.
Likewise the time that date displays depends on the time at which you launch it. If the minute hand in gworldclock ticks at 8:03:50 then yes, gworldclock will display 8:03 while date displays 8:04 for 50 seconds until the next gworldclock update. The only way to stop the aliasing is to first set a temporary timer in gworldclock waiting for the true minute hand to strike, and then set up the 60 second timer. This would have to be done each time the data format is changed from seconds display to minutes (no-seconds) display. Since one of the reasons for not displaying the seconds is that you really don't care that much about to that degree of accuracy, I'm not entirely convinced it's worth complicating the timer handling to deal with it. I'll leave the bug open a little while longer while I think about it. Thanks for using gworldclock, I hope you continue finding it useful even if the minutes do not tick at 00 seconds. Drew -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
