On 10/03/2017 11:04 PM, Alex, VE3NEA wrote:
Hi Alex & all,
Usually, when I have to test the validity of a callsign, I use the perl
regular expression:
^((([A-PR-Z]+[0-9]*[A-Z]?)|([1-9][A-Z]+[0-9]*))\/)?(([A-PR-Z]+[0-9]+[A-Z]+)|([1-9][A-Z]+[0-9]+[A-Z]+))(\/([PMA0-9]|MM|(([A-Z]+[0-9]*[A-Z]?)|([1-9
WSJTx could suppress invalid messages like this:
203500 -19 0.1 513 ~ CQ 02E4/XX4IWT JO12 !where?
by performing a simple validation of type 2 prefixes. A valid prefix has one of
these patterns:
@ @@ @@# @@#@ @# @#@ @## #@ #@@ #@# #@@#
where @ is any letter and # is any digit, and the first
Another observation.
Scenario:
I'm following a QSO between 2 other stations. Before the station I'm
interested in contacting sends his/her final 73, I set everything up for a
tail ending call.
However, when the 73 message is received, Tx is disabled, and I have to
click enable Tx again, possibly
> On Oct 3, 2017, at 6:18 AM, DXer wrote:
>
> The following situation occurs when Call 1st is selected.
While I did use Call 1st when it was first introduced, as soon as the mode
became popular I unchecked that box and never went back. I get 3-4, sometimes
more replies if I CQ. Directional
The following situation occurs when Call 1st is selected.
I call CQ, two stations answer, Call 1st 'engages' with one of the
stations, but I want the other one. The only way I found to override the
Call 1st choice is to stop Tx, click on the station I want , and start Tx
again. The time required t
On 02/10/17 01:15, Joe Taylor wrote:
> Hi David,
>
>> The real issue is the TX Enable. I’d like to avoid having it set on
>> the double click so I can pick the right time in the other QSO to send
>> my message, on a split frequency.
>
> Why not simply uncheck the box "Double-click on call sets T
