[New Feature] Add custom Self Spotting details after trigger Keywords QRV, QSY, QRT

PoLo - Issues & Ideas
,
1

Currently, there are short cut commands for entering non-callsign details in the THEIR CALL field that save the operator needing to open up specific sub-fields. This is quite handy when running multi op POTA and especially when using an external keyboard.

Enter QRV, QSY, or QRT to self-spot with the respective comment. Enter SPOTME or SPME to self-spot with current frequency and mode but no comments.

Ref: Tips and Tricks | Ham2K Portable Logger

In support of quick field selection, a user can use the SPACE bar instead of TAB to move around to various fields.

Use the [space] key to quickly select the next field in the form. This is especially useful when you are logging a lot of contacts and want to keep your hands on the keyboard.

ref: Tips and Tricks | Ham2K Portable Logger

However, sometimes an operator may want to add additional comments to the Self Spotting details. Currently this would mean pressing the SPACE bar after the keyword and between subsequent words, which would boot you out of the field and trigger the self spot prematurely.

Perhaps when the THEIR CALLSIGN field contains some of these key triggers, then a single space would add additional comments to the SPOT ME field. When the comment is complete a DOUBLE SPACE could trigger the jump to the next field.

This might look like

“QSY from doing a bit of hunting on the bands[SPACE][SPACE]”

This might actually open up the opportunity to perform multiple actions in a single THEIR CALL field entry:

  • entering the call sign would obviously be added to the QSO record
  • Entering a SPOTME keyword followed by comments would provide hunters context
  • Adding op/[CALLSIGN] could add a second operator
  • Perhaps note/ or /nt shortcut could produce a new note

Sample entry:
VE3FCQ QRV just finished up lunch and bio break op/ VA3TXL[space][space]

Anyhow, just trying to maximize some of the features that already exist while trying to streamline solo and multi-op scenarios.

Thanks for your consideration.

1 Like
2

I’ve been thinking about ways to do some of these things, like allowing spaces in shortcut commands.

But I fear that can make processing of the callsign field exponentially more complex, in particular if you can combine callsigns, commands, and extra info in a single line, where the ordering of operations might create problems.

I have also been thinking about making a separate “exchange” field, instead of just “state”, where you can enter state but also contest exchanges, notes, pota or sota references, etc.

As for …

  • Adding op/[CALLSIGN] could add a second operator

… you can already do that, using commas to enter multiple callsigns. It even works when editing existing QSOs. (And if you mean second operator on the logging side, entering the second op on every QSO is not the way to go… just log once, and then at the end export the log, change the operator in the operation settings, and export a new log)

Maybe for now I can try to figure out a way to do spaces in comments for spots.

3

Thanks @KI2D ,

I wonder which problem is harder to solve. Parsing complex text or fixing the tab order issue. Both problems seem to be impacting potential future features.

As previously noted I would +1 the “Smart exchange” field

l did see the documentation for op/CALLSIGN feature. I was just trying to illustrate that a single string could include multiple commands.

As for the second operator condition this was my experience on Friday introducing another operator to POTA and my setup. Throughout the day I experienced the following scenarios:

  • I was operating and my friend was observing
  • I then brought my friend on as second operator
  • My friend then had to head home for a bit
  • My friend was then working as first operator and I was second operator

Given the mix of the above scenarios I had to spend a chunk of time manually editing the ADIF ensuring that only valid records remained.

Having a way to note when new operators come into and out of the operation would be useful, especially for events like field day or club outreach events that may also include GOTA station(s).

Thoughts?

4

I love the idea of “solving” the “second operator problem” on the local side. (Commas solve it when there are multiple operators on the DX side)

Allowing for a comma-separated list of calls in the “OPER” command, and in the Operator setting, seems like the way to go.

You can even edit the operator in the “More” section.

And the recent work refactoring all the log generation and adding a dedicated screen for that will help in dealing with log exports.

I’m going to tag this as “ready-to-implement”.

Now the hard part is finding time to work on this, among all the other priorities.

5

If this were me, I would have just created a second operation (for two ops) and switched between the two. I like to keep things simple instead of remembering and typing complex compound commands like that. But that’s just me.
There is no onscreen confirmation that the compound command switch has been made and not much room to ever show it. But the operations can be given different note entries to assist identification.
Alan