On 28/02/2018 14:40, Black Michael wrote:
At least for me JTAlert now starts WSJT-X just fine...nag window of
course stays until clicked.
If your intent is to break JTAlert starting it up I guess you'd better
break it again....but this is the way it should nag IMHO and not have
such side effects.
de Mike W9MDB
Hi Mike,
if it has had the side effect of not interfering with JTAlert starting
WSJT-X for you then that's fine. I suspect it is more subtle than that
as JTAlert latches onto any window with the right title so the timing of
JTAlert looking for a window and the timing and ordering of the windows
created by WSJT-X is probably a race condition. Either way it is not an
issue. As beta test versions may crash I always start WSJT-X on its own
and likewise with JTAlert if I am testing on air and want alerts and
automatic logging through to DXKeeper.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
