Dear Bill
Thankyou for your swift response.
It does not create a new mis-spelled configuration because it wipes the
WSJT-x.ini which then of course contains no configurations.
As this works perfectly with properly spelled configuration names and is
reproducible , I am inclined to believe that I am not doing anything wrong.
I appreciate your point about reading the internal .ini file. I agree and am
not but was looking there for clues.
I need a way of synchronising the list of available configuration names in the
WSJT-x client with my companion software which does not involve my users (mis)
typing them or selecting recently deleted configurations and then crashing the
client.
I would obviously prefer a UDP solution :-
1. Currently message type 14 .Send seems to return the message length
regardless. Could it return (say) -1 on failure (and not crash the client) ?
2. I am aware that the Status (1) message contains the current configuration
name. As well I really need a list of available configuration names. If this
cannot be deduced by my (reluctantly) looking in .ini files or the registry,
which as you say defeats the object of using a networking protocol, then my
request is that you create a new message type for this.
Many thanks for your patience. I am not complaining, it's really great
software and a pleasure to use.
By the way if you have time look me up on QRZ.com and play my (bad) video to
get an idea of where I am going with my so far un-named WSJT companion. I am
looking for beta testers.
73 and Stay Safe de G4SWY Del +++
On Wednesday, 24 February 2021, 10:00:08 GMT, Bill Somerville
<[email protected]> wrote:
On 24/02/2021 05:12, Derek Turner via wsjt-devel wrote:
> Dear Developers
>
> I have discovered (painfully) that if I mis-spell the configuration
> name in message type 14 then the WSJT client resets itself and clears
> WSJT.ini back to its installation settings.
>
> Where in WSJT.ini or elsewhere can I find out what are the active
> configurations ?
>
> Many thanks.
>
> 73 de G4SWY Del +++
Hi Derek,
that sounds wrong, are you sure it it is not just creating a new
configuration with the misspelt name?
You should not be reading the WSJT-X.ini file it is internal to WSJT-X,
for a start the format is subject to change without notification, and
secondly doing so defeats the object of using a networking protocol.
The current configuration name is included in the UDP Status(1) message.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
