Quoting "take any explicit action required."
The ALL.txt file is available to scan through with a simple
DOS batch file. You want a low overhead scanner.
With POWERSHELL there's a cmdlet Start-Sleep.
"The Start-Sleep cmdlet suspends the activity in a script or
session for the specified period of time. You can use it for
many tasks, such as waiting for an operation to complete or
pausing before repeating an operation."
So run a Start-Sleep cmdlet that sleeps for a few seconds
and then scans ALL.TXT for any particular DXCC prefix.
Usually you already know when an All Time New One is going
to be up and so you scan specify one or more prefixes to
scan for. You may want to use another Powershell command
such as Get-Content to isolate with -Tail in order to quit
scanning the "old" portions of ALL.txt to avoid getting
endless reminders after the New One pops up the first time.
--73, Glenn, AF8C
On 4/4/2023 9:39 PM, john via wsjt-devel wrote:
It would be nice to have a special alarm for when wsjt-x spots an "All
time new country"
Any way to set an alarm in the current version?
John
KW7A
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: Joe Taylor via wsjt-devel <wsjt-devel@lists.sourceforge.net>
Date: 4/4/23 6:54 PM (GMT-07:00)
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Cc: Joe Taylor <j...@princeton.edu>
Subject: Re: [wsjt-devel] Feature or Flaw
Hi John,
As has been stated many times, both here and elsewhere:
When exchange of standard QSO messages does not go as expected, it's up
to you to take any explicit action required.
Auto-sequencing is an operator convenience, not an operator replacement.
-- 73, Joe, K1JT
On 4/4/2023 6:20 PM, John McKee via wsjt-devel wrote:
> I tried sending this from my gmail account, and it was held for review,
> presumably because I am not registered with WSJTX under that account.
> So, I am sending it again under my att.net <http://att.net> account for
> your review:
>
>
*****************************************************************************
>
>
> I was today attempting a QSO with ZD7CTO, and after a long series of
> calls to him, I finally received a response at 213015 to which I replied
> at 213030. No response from ZD7CTO, so I sent two more responses at
> 213100 and 213130. Then, the WSJT-X changed me from Tx 3 to Tx 1, and
> began the QSO process again as seen at 213200… this happened several
> times more, necessitating my repeatedly changing to Tx 3 to complete the
> QSO finally at 213930……
> My question: is this a feature (being changed back to Tx 1 after a QSO
> is answered by the DX station), OR is it a flaw in the program??
> John, NT5EE
> 452EA862503543238BA3234D848ABD1F.png
>
>
>
> 1F58A8AEC7204CED928B6084F5ABF298.png
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
This email has been checked for viruses by Avast antivirus software.
www.avast.com
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
