12 noon showing as 12AM, and 12 midnight showing as 0AM
Hi! Relatively trivial issue here, but hopefully also just as trivial of a bug fix on your end. It would appear that the 12 o'clock noon hour is incorrectly being displayed as 12AM rather than 12PM when the clock is set to 12hr mode. And 12 midnight displays as 0AM rather than 12AM. Thanks!
Comments
-
I believe this was a bug in an older version of SecuritySpy, which has now been fixed. Are you sure you are using the latest version of SecuritySpy? If you are seeing this problem with the latest version, please let me know and I will investigate.
-
Looks like I am running version 4.2.6 and when I tell the app to check for updates it says I am already using the latest version of SecuritySpy. Is this actually the latest version? Or do I need to manually download an update from somewhere?
-
Yes, version 4.2.6 is the latest version.
Could you please clarify exactly where you are seeing this anomaly in SecuritySpy? There are many places where the date is displayed (e.g. text overlay to video images, Browser feature, web interface etc.) and we need to narrow this down a bit in order to investigate. -
I am seeing the issue in the Text Overlay on both video and still image captures as well as the live stream. I have the value of the Text input field set to the default of "+d", Font Size of 30, and Position of Bottom Right. FWIW, I'm on macOS 10.13.6, I have tried manually setting the system time and I can reproduce the issue during the midnight or noon hour (whether set manually or via NTP), and I have tried restarting the app as well as the system just to be sure there wasn't some weird cached setting or something. No change.
-
OK, thanks for that. I have now fixed this in the latest beta version of SecuritySpy (currently 4.2.7b5). Please confirm.
-
Thanks for following up! Just installed the latest beta linked above and the problem appears to have reversed. The midnight hour now shows as 12AM, but now the Noon hour shows as 0PM.
-
Sorry about that, I've posted a new beta (same link as above) that should now fix this - please confirm.
-
That did it! Thank you very much! I have since discovered an odd unrelated bug/feature but in the iOS app, so I will open a new discussion for that. Thanks again!
