Skip to content

Commit 6f5e4a7

Browse files
committed
@mbridak Documented Call History File usage.
1 parent 5f9485e commit 6f5e4a7

File tree

1 file changed

+45
-2
lines changed

1 file changed

+45
-2
lines changed

README.md

+45-2
Original file line numberDiff line numberDiff line change
@@ -828,7 +828,7 @@ change.
828828
I caved and started working on ESM or Enter Sends Message. To test it out you can
829829
go to `FILE -> Configuration Settings`
830830

831-
![Config Screen](https://github.com/mbridak/not1mm/raw/master/pic/esm_config.png)
831+
![Config Screen](https://github.com/mbridak/not1mm/raw/master/pic/configuration_options.png)
832832

833833
Check the mark to Enable ESM and tell it which function keys do what. The keys will need
834834
to have the same function in both Run and S&P modes. The function keys will highlight
@@ -872,7 +872,50 @@ QRZ (for Run) or Exchange (for S&P) is sent.
872872

873873
## Call History Files
874874

875-
I've started work on using 'call history files'.
875+
I've started work on using 'call history files'. To test it, you can
876+
go to `FILE -> Configuration Settings`
877+
878+
![Config Screen](https://github.com/mbridak/not1mm/raw/master/pic/configuration_options.png)
879+
880+
Place a check in the `Use Call History` box. Call history files are very specific to the contest you are working. Example files can be obtained from [n1mm's](https://n1mmwp.hamdocs.com/mmfiles/categories/callhistory/?) website. They have a searchbox so you can find the contest you are looking for. If you are feeling masocistic, you can craft your own. The general makeup of the file is a header defining the fields to be used, followed by by lines of comma separated data.
881+
882+
An example file excerpt looks like:
883+
884+
```text
885+
!!Order!!,Call,Name,State,UserText,
886+
#
887+
# 0-This is helping file, LOG what is sent.
888+
# 1-Last Edit,2024-08-18
889+
# 2-Send any corrections direct to [email protected]
890+
# 3-Updated from the log of Marsh/KA5M
891+
# 4-Thanks Bjorn SM7IUN for his help.
892+
# 5-Thanks
893+
# NAQPCW
894+
# NAQPRTTY
895+
# NAQPSSB
896+
# SPRINTCW
897+
# SPRINTLADD
898+
# SPRINTNS
899+
# SPRINTRTTY
900+
# SPRINTSSB
901+
AA0AC,DAVE,MN,Example UserText
902+
AA0AI,STEVE,IA,
903+
AA0AO,TOM,MN,
904+
AA0AW,DOUG,MN,
905+
AA0BA,,TN,
906+
AA0BR,,CO,
907+
AA0BW,,MO,
908+
```
909+
910+
The first line is the field definition header. The lines starting with a `#` are comments. Some of the comments are other contests that this file also works with.
911+
This is followed by the actual data. If the matched call has `UserText` information, that user text is populated to the bottom left of the logging window.
912+
913+
So if one were to go to `FILE -> LOAD CALL HISTORY FILE` and choose a downloaded call history file for NAQP and typed in the call AA0AC while operating in the NAQP, after pressing space, one would see:
914+
915+
![Call History Example](https://github.com/mbridak/not1mm/raw/master/pic/call_history_example.png)
916+
917+
Where the Name and State would auto-populate and the UserText info apprears in the bottom left.
918+
876919

877920
## Contest specific notes
878921

0 commit comments

Comments
 (0)