locked Re: JTAlert causing DX Keeper to filter Log on Startup #DXLAB

HamApps Support (VK3AMA)

On 9/02/2020 8:01 pm, Stewart Wilkinson via Groups.Io wrote:
When my last attempt at a QSO in WSJT-X was incomplete and the Tx1 to Tx5 message boxes still have a callsign and report details that it was last trying to send when JTAlert starts it causes DX Keeper to filter the Log to show just the list of any contacts with the station I last tried to work, the only way to clear this appears to be to click the 'X' in DX Keeper to clear the filter. Starting 2 or more copies of WSJT-X and JTAlert causes the filter to change from one callsign to the next as each copy starts to work. 

Is there a way that I've missed to clear the incomplete QSO data from WSJT-X or from JTAlert to stop this happening ?

If you don't want JTAlert performing a DXKeeper lookup (along with DXK filtering) on startup make sure the "DX Call" field in WSJT-X is empty. JTAlert has no way of knowing if that DX Call is a new entry or an old entry from a previous session.

de Laurie VK3AMA

Join Support@HamApps.groups.io to automatically receive all group messages.