On 3/12/2016 4:52 PM, Black Michael wrote:
Well...each UDP version# would match whatever "change" is introduced
that would/could/should affect external apps.
The only problem with the rev# is that may well get reset at some
point in the future.
And the build version isn't any more likely to change when something
new is introduced...at least not in the development versions.
If we ever switch to git the rev# will disappear completely though I
guess we could change then to our own one-up number to continue it.
de Mike W9MDB
Hi Mike,
I understand, especially about Git commit strings, eg. from one of my
repositories... "d79c7aa89d8b643ddc43a8f5dbed9b0f4dae22e7".
What is needed is some way to uniquely identify the version/build being
used. An auto-incrementing integer would probably be the best as it
would make the code check trivial.
IMO, if it is important enough to have the version number in the window
title and the build number in the "About" window to uniquely identify to
the end-user which version/build they are running, then someway to
expose this uniqueness in a UDP message needs also to be available.
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
