Time requires seconds

Bugs
#1

Just trying out the new beta! Very excited to see your new work.

The time seems to require seconds. Maybe this is a feature request rather than a bug. Could it not require them?

I was making a contact and didn’t save it right off while I was trying to figure out the park. After I paused the clock I edited the time to be “a few minutes ago” but it refused to save due to an invalid time. After I added seconds, it saved.

#2

Bug. I’ll get it fixed!

#3

Release 2.6.4

  • Fixed: only require HH:MM for QSO Time On
  • Fixed: refetch stale QRZ session key if error returned
#4

So I’m embarrassed to admit how often I’ve done this, but I almost always forget to resume the time when I pause it for some reason or another. Could there be a more visible reminder perhaps that the time is currently paused?

#5

What if I flipped the indicator color? Red is off.

#6

Flipping the color might work if it were a more visible red.

#7

It’s coming out shortly with another fix. If you’re still not happy with it, open a new thread as this one is about to close.

#8

Thanks! We’ll see if that gets my attention. :slight_smile:

#9

I mean, let me know if not. I’m not sure what I’ll do but open a thread for sure. . It use to subtly pulse in the early days but that annoyed me too much :slight_smile:

#10

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

#11