PathFinder to WW resolved by setting the options in the WW config Log tab. seems these are unset when this procedure is used. Start all DXLAB modules from Launcher. After completion, close down Commander and WW. Start N1MM to run while the remaining modules are active. After terminating N1MM session. restart WW and Commander from Launcher At this time it would appear that all the WW Log options are cleared, therefore WW does not see any lookup return PF to WW.
In PF the Config button is not opening the config screen
PathFinder to WW resolved by setting the options in the WW config Log tab. seems these are unset when this procedure is used.
+ That's not correct. The options in the "QSO Info" panel on the Log tab of WinWarbler's Configuration window are saved to the Windows Registry when WinWarbler is terminated, and restored from the Windows Registry when WinWarbler starts.
+ Directing the Launcher to load WinWarbler's settings from a Workspace while WinWarbler isn't running could change the options in the "QSO Info" panel the next time WinWarbler starts.
+ Is there an errorlog.txt file in your WinWarbler folder? If so, please attach it to an email message and send it to me via
aa6yq (at) ambersoft.com
73,
Dave, AA6YQ
Start all DXLAB modules from Launcher. After completion, close down Commander and WW. Start N1MM to run while the remaining modules are active. After terminating N1MM session. restart WW and Commander from Launcher At this time it would appear that all the WW Log options are cleared, therefore WW does not see any lookup return PF to WW.
Thanks for responding Dave. The PF Config window was minimized to the task bar. The above procedure of shutting down WW, running N1MM and then restarting WW did not cause a reset of the WW log options in tests from startup.
Thanks for responding Dave. The PF Config window was minimized to the task bar. The above procedure of shutting down WW, running N1MM and then restarting WW did not cause a reset of the WW log options in tests from startup.
