Hi Joe,
the reason some modes are witching on monitor is because they have
working frequencies defined. The switching on of monitor is a side
effect of changing frequency.
73
Bill
G4WJS.
On 08/06/2016 22:11, Joe Taylor wrote:
Thanks... and yes, please look into it!
-- Joe
On 6/8/2016 5:06 PM, Bill Somerville wrote:
>On 08/06/2016 21:43, Joe Taylor wrote:
>>In WSJT-X r6739 if you have Monitor stopped and then switch mode to
>>JT65, JT9+JT65, or WSPR, Monitor is turned on. Switching to JT4, JT9,
>>ISCAT, JTMSK, or MSK144 does not turn Monitor on. This seems illogical.
>> Was there a good reason that I've somehow forgotten?
>
>Hi Joe,
>
>I can't think of a reason. It is not immediately obvious to me how it
>does get turned on when switching to JT65 or JT65+JT9. I can look into
>it further unless you already have that bit sorted out.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
