The wsjtx process creates control files .start, .stop, or .quit and
the jt9 process deletes them. This is intended to avoid any race
conditions that get the processes out of sync.
On the Fortran side:
- For the nzhsym=41 activation, bail out if m_ihsym reaches 45
- For the nzhsym=47 activation, bail out if m_ihsym reaches 48
- Change the format and content of what's written to fort.71
- Change msdelay from 10 to 1
In mainwindow.cpp:
- change format and content of what's written to qDebug
- always start FT8 decoder at m_ihsym = 41, 47, and 50
- don't start function decode() is decoder is already busy
- send updated m_ihsym to jt9[.exe] via ss(1,1). Bill won't like this!
- jt9 bails out of the 41-buffer pass at m_ihsym=45.
The Status(1) message acquires the new fields Frequency Tolerance, T/R
Period, and Configuration Name. The Rx DF, Tx DF fields become
unsigned (this should be a benign change which is just for correctness
as -ve values have never been possible).
The Close(6) message becomes bi-directional allowing external
applications to gracefully close down WSJT-X instances.
A new message SwitchConfiguration(14) is provided that allows an
external application to switch the current configuration of a WSJT-X
instance.
Another new message Configure(15) is provided to allow external
applications to adjust some key parameters like the mode and submode.
See the NetworkMessages.hpp header commentary for full details. The
UDPExamples/MessageAggregator reference application has been updated
to be able to exercise all of the above changes.
Note that this commit enforces stricter checking on the
"Settings->Reporting->Allow UDP requests" option, which must be
checked before any state changing incoming messages to a WSJT-X
instance are processed.
This include inverting the order of table view rows so the newest is
at the top, without that the Qt MVC interactions when using a database
table based model is too slow and complex to manage.
The table views now have sort by column capability in the normal way
(click column header to reverse sort order) for timely logging and
non-disruption of Tx starts the log view should be sorted in
descending time order and scrolled to the last row added. Without that
Fox and contest logging will work but serious delays may be invoked
that disrupt operation.
Move to OnRowChange edit strategy for log tables so that deletes from
view can be implemented cleanly.
Improve layout of log view tables by resizing to contents.
This change incorporates a reorganization of the GUI code with
widgets, validators, models, and item delegates being moved to
sub-directories.
Relax the requirements of the ForeignKeyDelegate and related
CandidateKeyFilter classes to allow them to work with constant model
pointers for both referenced and referencing models.
