Actually I think we need a separate version # in the UDP status message.If we
ever change CM methods the rev# is likely to change in a non-logical manner
(like changing over to git).I think a manually changed# in the UDP protocol
would seem more appropriate.So any change in behavior that would affect
external apps or changes to the protocol like adding fields would simply bump
up the #A 32-bit int should cover us for quite a while.
de Mike W9MDB
From: "Laurie, VK3AMA" <vk3ama.ham.a...@gmail.com>
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Sent: Friday, December 2, 2016 4:59 PM
Subject: [wsjt-devel] Request: Expose WSJT-X version & build numbers in UDP
Status message
Please consider adding the WSJT-X version and build numbers to the UDP Status
message.
There have been times where I have needed to know these values to permit
programmatically altering JTAlert behaviour based on the WSJT-X version/build
numbers. I can get the version number by scraping the value from the Gui title,
but that is not ideal. There have been times, especially with so many users now
running pre-release version of WSJT-X that I have needed to know the build
number to alter JTAlert behaviour.
Thanks
de Laurie VK3AMA
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
