This is an edge case when working a call like RI9F/GM4WJS where it is
not possible to confirm receipt of the full compound callsign in a Tx5
73 message as "RI9F/GM4WJS 73" is 14 characters.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8111 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
This allows UDP servers to emulate keyboard modified double-clicks on
decoded messages, E.g. ALT+double-click for replying to a CQ or QRZ
call without changing ones Tx frequency offset.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8103 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Extended the Decode and WSPRDecode UDP messages with an "off air"
boolean field indicating the decode was derived from a .WAV fle
playback rather than an on air reception.
Extended reference applications to use the new off air decode message
field.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8092 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Right-click either decoded text window to erase its contents. The
"Erase" button on the main UI still operates as before although it is
implemented differently now.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8090 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
The main window font has to be set after main window construction
otherwise the menu bar font does not get set.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8077 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Slower decodes may mean that confirmation that a called station is
working another station arrives after start of Tx.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8071 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
We cannot assume that a "DE <dx-call> <anything>" is or is not for us
so we must continue calling and risk possible QRM. Calling split
avoids this issue.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8066 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
These attempt to ensure that a prefix is logged by the QSO partner
even if the compound call holder user Tx3 to tail-end a QSO.
The type 2 message generation options are largely overridden in
contest mode as only a few options make sense. Key is that Tx1 may use
only the base call when calling split is necessary, this requires that
both Tx3 and Tx4 have the full compound call otherwise the QSO partner
will never see the full call until it is possibly too late i.e. post
logging.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8065 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Message generation in contest mode now generates the correct Tx3 for
type 2 calls.
"<type-2> 73" is a free text so needed special handling in message
processing.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8064 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Generic message packing and unpacking routines now understand antipode
grid contest messages. These messages are now recognized as standard
messages in message response processing and dealt with appropriately
when contest mode is selected and applicable (currently FT8 and MSK144
only).
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8062 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Double-clicks on 73 messages fixed. Fixed issue with incorrect decode
being selected by double-click. Refined auto-sequencing sign off
handling, any 73 or rr73 free text near Rx or Tx frequency taken as a
73 from QSO partner but if a standard message then must be from QSO
partner.
Moved functionality from MainWindow to DecodedText class.
More efficient picking of messages from decoded text windows by
extracting the text block directly.
Tighten up use of RR73 and skipping Tx1, these are now disabled for
relevant compound calls where they would break the QSO exchange.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8056 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
73 messages from other QSOs on frequency should now be ignored rather
than being processed.
Also some long overdue refactoring and tidying of non-idiomatic C++
code in the logbook directory.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8047 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
This means that "CQ DX", "CQ VT", etc., will be presistent until changed back.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8035 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Note that reverting to v1.7 will invalidate any saved working
frequencies from v1.8 but proceeding to v1.8 again will present a
reset set of working frequencies i.e. any user defined entries in v1.8
will be lost of a v1.8 -> v1.7 -> v1.8 transition is made.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8018 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Holding down the SHIFT key while tuning the rig should update the
nominal sked frequency, not holding done the SHIFT key should not
update the sked frequency. This is not yet perfect and sometimes a
change to the nominal sked frequency can get through but it is a rare
as yet unfound race condition.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@7992 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Call first combined with "Lock Tx=Rx" (why would anyone consider doing
that!) should continue on the Tx frequency of the station being
worked and not be switched another calling station's frequency.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@7972 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
FT8 auto-stop will only react to messages within +/- 50Hz of our Tx
frequency.
Auto-sequence on "DE ..." and free text 73 messages will respond if
they are within 25Hz of our Tx or Rx frequency.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@7970 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Bad idea, need to find a better way to extend grids to 6-digits from
CALL3.TXT.
This reverts commit r7959
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@7965 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Required to pick best AP masks in FT8 decoder
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@7958 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
The UDP decode and reply message have been augmented with a boolean
flag denoting a low confidence decode when set. Existing clients can
safely use the reply message without passing the flag as the default
value will still action messages that have high confidence. If low
confidence decodes are to be passed back via the reply message then
the low confidence flag must be included and correctly set to match
the original decode.
See NetworkMessage.hpp for message fields and meanings.
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@7957 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
