(12-09-2020, 06:18 PM)EA3GCV Wrote: Erik,
I focused my explanation on these pair of settings but it applies the same to realtime setting (when QSO Entry shows up it reads this setting as well). Realtime setting must be set off automatically while saving QSOs from JTDX because date/time are assigned by JTDX. Once the QSO is saved it's restored to user setting even if the UDP link is on. This is the only difference of behaviour against the other pair of settings. Before this beta I restored all 3 settings after saving QSO or QSO is cleared from JTDX. I could, of course, do the same and maintain realtime off during the UDP link (as I'm now doing with the other pair of settings) but I think this really doesn't matter. That's why realtime acts immediately if user changes it. Other pair of settings are most important related to mode handling and I have to keep them during all link to avoid this issue. Mode most follow the linked program and Swisslog handles all this automatically despite user settings. Once UDP link is disabled or JTDX closed, realtime setting is restored to the same state as when QSO Entry showed up (the same as other pair of settings). It's the only way I have to set these settings again in the same state they were before linking to JTDX.
Best 73
I was not referring to the operation of Real Time setting in relation to JTDX. Only that a user will find that this acts immediately as he sets it thus causing the belief that the other settings will do so too when in fact they do not. It is a matter of consistency to avoid confusion. I cannot think of any other software where a panel or window of configuration settings has a mixed method of implementation. Anyway, I know this now and the latest beta solves the issue. Thank you. I suspect Roland's problem is more related to the choice of internet database being searched. HamQTH for example is definitely flakey.
