Adding the ADIF filed to every saved ADIF would save a lot of work.
The field is used to add messages to the QSO fields on f.e. eQSL and Hamlog. It’s most often used to add the activated reference(s) or aditional info to eQSL and Hamlog (it’s displayed in the 3th line of the QSO field)
Not quite sure what you mean by 3rd line of QSO field. It’s certainly an additional ADIF field.
It could be added to the Operation Details form and would be a static value for the operation.
I have a database trigger in my HRD setup to fill that field for me when I import. Saves me a lot of work for eQSL.
Alan
So e.g. for P2P contacts, my eQSL message is generated with my park name and ref and their park ref:
That’s how my eQSL looks like when is in the ADIF file
When no the eQSL only has 2 lines , the QSLMSG is displayed on the 3th line if the ADIF field is in.
With current PoLo I have to add the QSLMSG field after the activation (with ADIFMASTER). If the activated references would be saved in PoLo into every log in in the field, that would save a lot of time. And it will avoid many eQSLs or HQSL (Hamlog) send without any reference displayed!
Obviously you first import to HRDlog and from there you send the eQSL. I import the ADIF to eQSL directly as saved by PoLo …
73 ON4VT aka OT4V
Quite right. Everyone may have their own take on how this is formatted etc.
So PoLo would also have to create a way to populate the field for you to save copying it down the log manually. There may be a fair amount of work to create the interface which enables this kind of field population that suits everyone’s personal taste.
I assume that when you make the QSLMSG standard the activated references, it would be already a very big step forward. At the first place customizing the field might not be needed ?
Sure - but I suppose a standard that suits most people may be hard to decide on. Not sure I would move away from my standard but an arbitrary standard may encourage more people to use the feature.
There are plans to add a “template format” for things like adif fields, spot messages, etc.
This would work perfectly for what is discussed in this thread.
But it’s not trivial work. Not so much in the templating code, but in the UI needed to allow users to define where they want to use it.
So don’t expect it in the next month or two, because there are other priorities, but it will come sooner or later.