JTDX on-top ...
|
Peter Eckersberger
Hi Bob,
In the meantime I'm convinced it was me in making a mistake in interpreting the manuals text. For one reason or an other I thought for "parallel logging" only the "TCP"-feature has to be active. Which means in other words no UDP needed at all. Just starting Logger32 and in a second step starting JTDX e.g. by its own program icon. BUT ... For starting JTDX on top one needs the UDP-bandmap and its start menus. By doing it that way everything is working fine. Sorry for the inconvenience stealing your precious time. 73 de Peter, OE3EPW
|
|
|
|
Bob
Peter, your pictures show that JTDX is not starting on top. The JTDX title bar shows JTDX by HF community. Maybe Logger32 started JTDX, but is did not control it. On the UDP BandMap, click the START/STOP menu. Click DELAY AFTER STARTING JTDX. Set the time to 20 seconds (or maybe more). Now, after starting JTDX from Logger32 does the title bat say JTDX & Logger32 (on-top). SeventyThree(s).
|
|
|
|
Peter Eckersberger
Hello Bob,
Sorry I'm late. Have been out of my home. To answer your question ... YES, its ON TOP. Here some pics ... That's the one where only 'TCP' is on. But no 'UDP" ... therefore no 'band plan'. Parallel logging is OK, but JTDX vanishes every time at the end of every single logging procedure. That means ... 1 QSO logged and fiddling with the mouse to recall 'JTDX' to the foreground ... 
Here the start of 'JTDX' via 'start menus' within 'band plan' ...  This shows the activated 'ON TOP' switch ...  Finally the operating position when 'JTDX' and Logger32' is 'parallel logging' ...  Well, that's it. Hope you're getting the point. 73 de Peter, OE3EPW
|
|
|
|
Bob
Is Logger32 configured to start JTDX 'on-top'? SeventyThree(s).
|
|
|
