Time stamp (regression)

This appears to be a bug that has reappeared.

I’m not sure when this reappeared, but earlier versions of HAMRS would update the QSO time once the user tabs/advances to another field other than the call sign.

0.11.3 retains the time stamp indefinitely. In fact, I created a log in HAMRS, activated an hour later, and my first QSO ended up with a time stamp that was off by one hour.

It appears this may bump someone who believes they achieved an all-time-new-one status at a park to the back of the line if a later activator on the same day creates the log much earlier in the day.

More importantly, time stamps may not align and grant park to park credit, or could cross UTC boundaries and yield a failed activation.

(Observed on iPad OS)

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.