(12-09-2020, 01:05 AM)EA3GCV Wrote: Hello,
I have revised carefully all code related to this and I found out that the "Set mode from QRG" user setting was not saved when linking to WSJT-X. I have also improved some other things. Please try this new beta and let me know:
www.swisslogforwindows.com/Beta/SwisslV5.exe
Best 73
Hello Jordi.
I do not see any difference from before in the latest beta. I set to on (checked) the two settings I referred to. JTDX starts and these two settings are set to off (become unchecked). When I close JTDX they remain off and do not revert to my choice of setting.
The problem of Swisslog locked into switching between RTTY and FT8 remains. I will try to explain it as an end user sees it - I know that from a programming aspect there is a world of difference. But still: if my transceiver goes to DIG mode, Swisslog quite rightly sets the mode to RTTY (it is the most common non-JT mode). But when JTDX attaches, Swisslog should not be asserting this mode because it cannot ever be RTTY (the mode does not exist in the WSJTx and JTDX applications). Swisslog ought to relinquish control of mode and start at the most common JT mode, FT8. But no, it stays on RTTY. Then it appears to fight with JTDX. I start a QSO and the mode changes from RTTY to FT8, RTTY, FT8 and all the while nothing else can happen. To me it appears as if JTDX has sent the mode but Swisslog tries to assert itself over JTDX, finally giving up and settling on FT8.
Meanwhile, the two settings are not reverting to being set on for me either. So after ending JTDX session I have to go back into options and turn them on again. I note you state only WSJTx but I presume JTDX should not be any different in behaviour. So I have no explanation, all I can say is that the problem persists.
I must just stress that my previous comments still apply. Although this beta is no different from the last, both afford an improvement over the original exe. There are some instances of saving QSOs where the problem does not manifest itself, just like before. Presumably the hiatus starts when Swisslog is fighting against JTDX and also engaged in other tasks like processing DX Spots.
