locked Issues Relating to Recently-Installed v2.50.0
I apologize for emailing you, but I have been unable to figure out how to post a ‘reply’ within any thread I read. There is no Reply ‘button’ as there is with other groups I belong to.
I recently installed JTAlert 2.50.0 and I love the new, flexible callsigns display. That is a great enhancement. Thank you for a fabulous upgrade.
However, I am running into some issues, namely:
Related to that last item, I would very much like to have actions for both single- and double-click, whereby a single-click on a station of interest focusses the RX frequency accordingly, and a double-click both focusses the RX frequency and enables TX. There are many times when I merely wish to observe a station for a brief period before calling – usually to wait until his current contact is finishing before calling. If, as I had thought, clicking actions are controlled solely by WSJT-X, then I will make my suggestion/request with that group.
73, and thanks again for all your efforts… Paul (VE3PS)
HamApps Support (VK3AMA)
My answers inline...
On 30/04/2021 2:18 am, Paul wrote:
Turn off the "Clear Callsigns display after logging" option in the main JTAlert Settings window, "Logging" section. Look under the "Logging Options". You will need to scroll the list of settings down to reveal the required checkbox.
Turn off the "Restore window when JTAlert is started" option in the main JTAlert Setting window. "Window -> Decodes" section.
Very likely you didn't perform the required change in JTAlert when switching WSJT-X to use multicast. Make sure the "Settings -> WSJT-X UDP Multicast on Loopback" menu of the main JTAlert window is ticked. The Help file (not the 2.50 features help) has instructions for the correct setup. See the "WSJT-X UDP Setup" topic (its at the root level) in that help.
The decision to go into transmit in response to a callsign click event is controlled by WSJT-X. JTAlert cannot control that behavior. There is no mechanism in the command sent to WSJT-X to tell it to go into transmit. JTAlert simply tells WSJT-X this Callsign of a specific decode was clicked. This is how the WSJT-X API is designed, there is no support within the API to instruct WSJT-X to go into transmit in response to a callsign click.
See my previous comment about API limitations in WSJT-X.
de Laurie VK3AMA