automatically selecting the appropriate WSJT-X Configuration when you switch primary transceivers in Commander
In its WSJT-X panel on the Configuration window's "Spot Sources" panel, the next version of SpotCollector provides an "Auto Config" checkbox whose explanatory popup displays
"check to automatically convey the name of Commander's primary transceiver to the local WSJT-X instance and direct that instance to switch to the Configuration matching the transceiver name".
What's "local WSJT-X instance " ?
Implementing this "automatic WSJT-X Configuration Change on Primary Transceiver selection" revealed that I had not yet fully documented SpotCollector's ability to accept connections from up to 16 instances of WSJT-X. These instances can be running on the same computer that SpotCollector is running on, or they can be running on computers network-connected to that computer. Because only one instance of Commander can be running on a computer, there are 4 types of WSJT-X instances:
A. one instance running on the same computer on which SpotCollector and Commander are running, using Commander to control its associated transceiver
B. multiple instances running on the same computer on which SpotCollector is running, each using its own functionality to control its associated transceiver
C. an instance running on a computer other than the one on which SpotCollector is running but with Commander running, and using Commander to control its associated transceiver
D. multiple instances running on a computer other than the one on which SpotCollector is running, each using its own functionality to control its associated transceiver
Type A - the instance of WSJT-X running on the same computer on which SpotCollector and Commander are running that uses Commander to control its associated transceiver - is referred to as "the local WSJT-X instance". This is what most of you employing direct interoperation between DXLab and WSJT-X are using - a single instance of WSJT-X that employs Commander to control the currently-selected primary transceiver.
have been updated to reflect the above topology.
When checked, the next version of SpotCollector's "Auto Config" box, automatically directs the local WSJT-X instance to select an appropriately-named Configuration when you direct Commander (running on the machine on which SpotCollector is running) to select a primary transceiver.
This new "Auto Config" functionality will not direct WSJT-X instances other than the local WSJT-X instance to change Configurations in response to primary transceiver changes, even if they are using an instance of Commander running on their computer for transceiver control. While doing so is technically feasible, the majority of DXLab users employing direct interoperation between DXLab and WSJT-X have SpotCollector, Commander, and a single instance of WSJT-X all running on the same computer; that's the configuration that the new "Auto Config" option will support.
After I complete additional testing here, I will send the new version of SpotCollector with "Auto Config" functionality to the participants in this discussion for their assessment.
If anyone encounters errors, omissions, or ambiguities in the updated documentation referenced above, please let me know. Thanks!