On 04/10/2020 15:56, Al Kozakiewicz wrote:
I’m with the N1MM development team.
We recently added support for the –language= command line token when
launching WSJT-X. Of course, WSJT is not backwards compatible, so
versions older than 2.2 error out on launch when appending the
command. I got around the issue by checking the last modified date of
wsjtx.exe, but this only works as long as there is only one version
dependence over time. It would be helpful if you set the program
version as one of the file resources either at build time or after the
solution is built.
To be clear, the version number needs to be known so the program can
launched with version specific options. The text in the heartbeat
message is of no use for this purpose.
Al
AB2ZY
Hi Al,
the main applications wsjtx, jt9, wsprd, and the application
installler/un-installer will have reasonably complete VersionInfo
resources in Windows builds from the next release.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
