Hi All,
thanks for the feedback during the contest activity and sorry for those
that have had issues that caused serious problems. Here is a summary of
the main issues with workarounds where available:
1) Having Tab 2 messages selected on the WSJT-X main window causes
contest exchanges not to be transferred to the Log QSO window which in
turn blocks logging a QSO until the exchange fields are filled in.
Workaround: Select Tab 1 messages.
This issue is due to insufficient testing being done with Tab 2
selected. It might be desirable for the ongoing development of WSJT-X to
remove Tab 2 from the user interface. Please respond if you feel that
Tab 2 messages are essential to your operating enjoyment and that Tab 1
is not suitable for you.
2) Editing data in the Contest Log window can leave the log table locked
and being unable to log QSOs. This defect is serious because there is no
indication to the user that there is a problem, the application simply
refuses to log what appear to be completely valid QSOs.
Workaround: If you get a message box saying "Invalid QSO data. Check all
fields" then single-click on a different row in the Contest Log window,
i.e. different from the last row you edited a field in; then log the
QSO. If you are not sure which row you edited, and there is no
indication to help with that, just try clicking on any row until the Log
QSO can be actioned.
This issue is due to an edit strategy on the Contest Log table's
contents that requires moving to a different row before changes are
committed. It will be changed to a commit on any field change strategy
which will fix this defect.
3) The QSO time field in the Contest Log window is incorrectly displayed
in local time despite the heading implying it is UTC. This is a cosmetic
issue as the underlying time is correctly stored in UTC. Unfortunately
this is compounded if one tries to edit the time as saving the edit
unexpectedly shifts the time by the local time offset.
Workaround: Don't attempt to edit the QSO time in the Contest Log
window. If you really think the time needs changing then fix it later in
the exported Cabrillo entry file.
3a) The QSO time field in the Contest Log window is displayed in the
regional time format your PC is set with. This format may be using a
12hr AM/PM time display, in fact that is the default for the "English
(United States)" region setting for MS Windows.
The next release will correctly show UTC with the time always in 24hr
format and edits will not unexpectedly shift the time when saved.
4) The band selector offered when editing fields in the Band column of
the Contest Log table incorrectly disallows selection of bands that have
been used in other QSOs.
Workaround: Don't edit the Band column in the Contest Log window, the
field is not currently used anywhere so its value doesn't matter. The
column will be used in a later versions to implement duplicate contact
avoidance.
5) The WSJT-X UDP protocol that allows applications like JTAlert to
interoperate with WSJT-X does not send the contest exchange details when
a QSO is logged. This means that those using JTAlert (and MacLoggerDX, I
believe) cannot use their logging application to keep and generate a
valid contest log.
Workaround: The direct UDP interface to N1MM Logger+ does transfer the
required exchange information.
If that is not suitable for you then the WSJT-X ADIF log file has all
the necessary fields and should be useable to generate a contest entry
file if it can be imported into your favoured logging application or as
a last resort manually.
The WSJT-X UDP protocol logging message will have the contest exchange
fields added for the next release of WSJT-X and cooperating applications
will be able to extract the required information.
6) Mac users who have a proxy connection to the Internet or are using a
VPN connection suffer a crash when attempting to download the LotW users
data, this happens automatically at start up if the file is not found in
the WSJT-X log files directory.
This is due to a defect in the Qt framework we use for cross platform
implementation. This new RC5 DMG installer has a fix:
https://www.dropbox.com/s/2m72gxalybwydzl/wsjtx-2.0.0-rc5-Darwin-qt5.9.dmg?dl=0
We have not replaced it on the project web site yet as it drops support
for OS X Mavericks (10.9) but the next release will be restricted to
10.10 or later unless more 10.9 users put their hands up with a good
reason why they cannot upgrade to a supported version of macOS.
Again, apologies to those trying to make a serious entry in the ARRL
RTTY Roundup using FT8 mode if you were hindered. All these issues will
be fixed for the next release.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
