On the contrary, it is necessary to support those users who do not wish for 
WSJT to start with the PC's locale. N1MM is localized and we launch WSJT with 
the same language N1MM is set to, which may not be the same as the PC.

For example, many Japanese users prefer English. Before we made this change, 
N1MM+ would start with English as the language but there was no way to start 
WSJT in any language except Japanese without the use of the -language command.

Al
AB2ZY

From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Sunday, October 04, 2020 11:31 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Set file version in program resources

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,

thanks for subscribing to the list.

There is no need to pass the --language=<lang-code> to WSJT-X to set the GUI 
language, that is done automatically according to the locale set in the 
operating system. There are only really two use cases for using that command 
line option:

  *   When testing and you want to select a different locale from the default 
just for WSJT-X,
  *   or when the user doesn't want the default, usually requiring the en-US 
default.

Seems to me that you don't need to worry about the former, and for the latter 
the user will only choose it is a translated UI is available. So you shouldn't 
need the version of WSJT-X to determine if translation is available.

The WSJT-X version is available in the WSJT-X UDP Message Protocol Heartbeat 
message. I realize that is too late for your requirement, but I don't think the 
requirement is necessary.

73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to