This isn't actually a problem. You have identified the changes that
will be required when 2.6 replaces 2.5. That is what RC candidates are
meant to do. So moving forward, with 2.6 GA, you should have a
seamless integration.
On 7/27/22 09:31, Sam W2JDB via wsjt-devel wrote:
Hi All,
Just an FYI regarding version 2.6.0 rcx and the prior release (2.5.x).
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.
If you are one that is using the new 2.6.0 rcx please be aware that
because of the way
the dev team updated the SplcOpr code values by inserting the ARRL
Digi contest before
the Fox and Hound values, there are a potential problems when
switching back and forth
between the two versions:
1. If you have a Hound configuration in the prior release (2.5.x), it will
come up as the Fox in the 2.6.0 xxx version
2. If you have a Fox configuration in the prior release, it will come
come up as ARRL Digi contest in the 2.6.0 xxx version.
3. If you created a ARRL Digi configuration in the new 2.6.0 xxx version
it will come up as the FOX in the prior release
4. If you created a FOX configuration in the new 2.6.0 xxx version
it will come up as the HOUND in the prior release
5. If you created a HOUND configuration in the new 2.6.0 xxx version
and that was the last configuration used when wsjt-x was shutdown,
The prior release will not start as it will detect an out of range
value
for the HOUND code.
73,
Sam W2JDB
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Jeff Stillinger - KB6IBB
KB6IBB Laboratories, Wylie Tx
http://kb6ibb-15.ham-radio-op.net/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
