Carry out the call history section directives
A call history file is built from years of logs, so its section and state columns carry old names, and the file says at the top what to do about that. The four lines that say it were read and passed over. All four are now carried out, in N1MM's order: !!MapOnSection!! stores the old Ontario sections as ON, !!ValidateArrlSection!! drops a section that is not one of N1MM's, !!GTA2GH_NT2TER!! stores GTA as GH and NT as TER, and !!Validate50State!! keeps a state, turns a section into the state it is in, or drops the value. The section list is the one N1MM's call history reader validates against, which is not the list its entry window offers: it holds the retired GTA and NT, and leaves out ON. It sits beside the reader in Nonemm.Core rather than with the contest lists, which are the entry window's. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RoGtneMQaz4M9w7Kk49AVD
This commit is contained in:
@@ -29,12 +29,6 @@ of an SO2R station cannot call CQ by voice. Alternating CQ therefore works on CW
|
||||
only, though nothing in it is CW-specific: a voice keyer that reports when the
|
||||
recording has finished would drive it as it stands.
|
||||
|
||||
**Call history: the section-validating directives.** `!!Validate50State!!`,
|
||||
`!!ValidateArrlSection!!`, `!!MapOnSection!!` and `!!GTA2GH_NT2TER!!` are read
|
||||
and passed over. Acting on them means holding N1MM's section lists and its
|
||||
rules about which sections are retired, and getting that wrong throws away good
|
||||
data. The file is read without them.
|
||||
|
||||
**The QTC window transmits on CW only.** The header, the lines, the QRV, the TU
|
||||
and the again messages go out through the keyer, with N1MM's messages and
|
||||
N1MM's defaults. Nothing goes out on SSB or RTTY: N1MM plays four recordings on
|
||||
|
||||
Reference in New Issue
Block a user