Having read and seen much of the same. I agree that F/H needs some
work. Andy is spot on about the user base not reading and following
instructions. Therefore, we do need forced compliance with the message
format. Of course there will be a lot of whining about it, but the
Clipperton
@lists.sourceforge.net]
Sent: Wednesday, January 24, 2024 5:48 PM
To: Brian Moran ; WSJT software development
Cc: Andy Durbin
Subject: Re: [wsjt-devel] Making F/H idiot proof
Hi Brian,
The screen shot and the discussion are in the Clipperton groups.io messages.
Clipperton is certainly using
AM
To: WSJT software development
Cc: Andy Durbin
Subject: Re: [wsjt-devel] Making F/H idiot proof
Hi Andy; can you please help me understand the circumstances better?
Under “normal” f/h operation, the hound calls with a grid. WSJT-X in fox mode
can queue a caller with a grid. WSJT-X in fox mode doe
Hi Andy; can you please help me understand the circumstances better?
Under “normal” f/h operation, the hound calls with a grid. WSJT-X in fox mode
can queue a caller with a grid. WSJT-X in fox mode doesn’t queue
non-grid-supplying callers.
If the “fox” replied to a signal report message as
As implemented in WSJT-X ver 2.6.1 the hound is able to select TX3 as their
first transmission. One user has posted a screen shot showing that fox replied
with a signal report but the QSO could not be completed.
Since new WSJT-X ops seem reluctant to read the instructions would the
developers
