After some troubleshooting I discovered that the time displayed in the app was not getting the NTP updates that the Windows system clock was receiving, meaning the app was "freewheeling" once started. So even though the Windows system clock is dead on with naval observatory time, the app is losing time.
Here is what I found, and would like some advice about:
The original code is using "get the seconds" to get the time in seconds and use that variable for some comparisons before putting it in a readable format. Example:
Code: Select all
put the seconds into NewTimeIn the process of discovering this, I found that the "time" function DOES receive system time updates, so I've managed a workaround that gets the date and time and converts them to seconds. Example:
Code: Select all
put the long date && the long time into NewTime
convert NewTime to seconds1) is there a cleaner way to do this? The code uses "get the seconds" in MANY more places, so before I go fix it everywhere I'd like to do it as efficiently as possible.
2) is this a known issue? I don't really know the differences in Mac (Unix) and Windows OS well enough to understand why the "get the seconds" command behaves differently between the two. It is kind of frustrating when trying to develop between the two platforms.
Would love to get your feedback! Thank you.