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.
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.
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?
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.