Hi Grant,
On 11/18/2019 4:20 PM, Grant VK5GR wrote:
Thanks for the reply - I am really pleased that the RR73 problem is in fact
a bug. I can tell you that it is driving FOX operators nuts on expeditions.
I guess we should have spoken up sooner.
Memo to file:
It's ALWAYS best to make relevant tests of critical software before
embarking on a DXpedition, and to communicate with the software authors
if issues are found. We could very easily have saved you lots of grief.
...
Bottom line - FOX operators need some channel awareness to avoid these
collisions. An in built band activity window is vital.
As for running a second instance, we did consider it - but facing fox mode
with 5 channels and hundreds of callers some of our laptops on the
expedition started to run out of grunt and screen real-estate given N1MM is
also active. To be practical, it really needs the band activity window
visible native in FOX mode within the instance the operator is running.
What you're requesting would also require screen real-estate. Making
visible just the Band Activity portion of a second instance's main
window would not require much screen space.
A better solution to your problem might be the one suggested by Iztok,
S52D: monitor the tail end of the ALL.TXT file. You could use the free
utility "BareTail". Or install the GNU utilities for Win32, for example
http://unxutils.sourceforge.net/ .
-- 73, Joe, K1JT
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
