Hi Christer.
Within the standard fldigi log it appears the RST in field can
save at least 9 characters. It might be possible then to do a
"log.get_rst_in", read the s/n? from "main.get_status1", append
that to the retrieved RST in then output to "log.set_rst_in.
ie the end result RST In looking like;
539 -7dB
Perhaps my old script could be modified to poll log.get_rst_in
whilst there is an active callsign being worked/logged and keep
updating the RST in field with an average s/n until the
<LOG:msg> and subsequent log clear.
Hope that makes sense. Operationally the idea then is to enter a
"Call" in fldigi then see the RST in repopulate every 10 secs or
so. The script just runs in background
Cheers/73 Bob
On 10/11/24 17:11, SA?PAL via groups.io
wrote:
toggle quoted message
Show quoted text
Hi Bob, you are in my log book 2023-04-18. Thanks for that,
it was enlightening and I learned a lot, since then I've been
using your script, I think it might be that I've tinkered with
it a bit, anyway I have a script that works fine on Mac OS.
Thanks for that! I'll take a closer look at the script and see
what I can do with it.
Despite that, I think it would be interesting if <LOG:msg>
could handle commands as well as random text, alternatively some
kind of pipe function, as I see it.
?
73/ Christer
