Beta Test the all new HAMRS

I’m not quite figuring out what the toggle QSO Table feature is. Could I ask for a bit more info?;

You can choose which columns to display in the QSO Table:

I have a ticket for logging multiple operators, but I haven’t sussed out how to implement it yet. Suggestions?

The toggle QSO table option is very cool. Thanks for the explanation!

On the multiple operator question, a few options occur but I’m not sure if they are good ones. One would be in the Entries list to add an option to duplicate and edit an already existing logbook entry. An alternative is contained in the Ham2K logger, which allows multiple callsigns to be entered in a log entry as a comma-separated list. There’d be some interface details needed there in terms of the name lookups. I guess another possibility would be to add a button to the logging entries to “save and keep” or some kind of similar wording that would not clear populated fields while saving the log entry.

Yeah, my thought was to do comma separated list like the park input, and just disable the operator info inputs - still do lookups, but whatever you get from each lookup is what is persisted at the time the QSOs are saved.

Sure, sounds reasonable

I’m working on the desktop builds this weekend, but I’ll swing back around to it. I don’t think it will take long.

Release 2.9.1

  • Fix: don’t populate Their State field when POTA park has multiple locations
  • Fix: focus ‘Their Callsign’ input after saving a QSO

Release 2.10.0

  • Feature: made QSO Map layers toggle-able

FYI the “won’t connect to qrz.com after an extended computer sleep” behavior still is present. I know to expect it, though, and am working around it without much problem.

Well that’s maddening. It should immediately refresh your QRZ key if it gets an invalid key error back. I’ll double check it.

Release 2.12.0

  • Feature: comma separated callsigns will now create multiple QSOs

Very nice!

One thing I noticed was that callsign and park lookups don’t seem to happen for the multiple QSO entries in the log. Could the computed state for the park be retained when an additional callsign is entered–it seems to be cleared now when the second callsign is entered?

The older version had a “lookup” button for entries in the log which served as a nice fallback when some piece of information wasn’t obtained. Maybe this would be useful to have again?

As a small feature request, would it be possible to have the selection of displayed log fields be retained between sessions?

Tell me more. Do you mean which fields you choose to show in the table?

Yes. It’s only a small matter though.

It’s doable for sure - is there a better ‘default’ I could set in the meantime?

I’m happy with what is there now. I suppose it might make sense to allow the other fields not currently included as initially-unselected options. The problem here though would be that it would take longer until enough qsos were logged to allow the full drop-down list to be shown.

Release 2.15.0

  • Feature: Spot yourself and others!
  • Feature: Added logbooks to quick search widget
1 Like