On 28/07/2022 12:31 am, Sam W2JDB via wsjt-devel wrote:
In testing the new releases and updating my companion programs that
are used by blind hams,
I ran across a backward compatibility problem with the special
operations codes/values used in
the UDP message.
While they have changed the special operation mode enumeration the
NetworkMessage.hpp file has not been update to reflect the changes. It
still shows the old enumeration...
* 0 -> NONE
* 1 -> NA VHF
* 2 -> EU VHF
* 3 -> FIELD DAY
* 4 -> RTTY RU
* 5 -> WW DIGI
* 6 -> FOX
* 7 -> HOUND
Testing has revealed the new enumeration is
* 0 -> NONE
* 1 -> NA VHF
* 2 -> EU VHF
* 3 -> FIELD DAY
* 4 -> RTTY RU
* 5 -> WW DIGI
* 6 -> ARRL DIGI
* 7 -> FOX
* 8 -> HOUND
This IMHO is a very bad design decision. Assigning the previous "FOX"
value is problematic. It will require that software authors create
WSJT-X version specific releases so as to avoid incorrectly reporting
and handling the new ARRL DIGI mode and treating it as FOX mode. This
will create support issues for software authors when an end-user
installs the latest 2.6.0 but doesn't update the other software at the
same time.
Software authors will need to hold back a compatible release until
WSJT-X is released with this breaking change. This will be a PITA
IMHO, the new ARRL DIGI mode should have been given a unique *previously
unused* number. It should have been 8 and the old 6 & 7 retained for FOX
& HOUND respectively.
de Laurie VK3AMA
(JTAlert author)
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
