Firstly, I know of the need to have Monitor off at startup to prevent
WSJT-X changing to the last used band. Why this behaviour has been
reintroduced with 1.5 is unclear. For me it is very undesirable. But
there is a more significant flaw associated with the Monitor button
activation. To reproduce...
1. WSJT-X with cat control (DXLab commander) and Monitor off at startup.
2. WSJT-X on 10m.
3. Exit WSJT-X
4. Change VFO to another band, say 15m 21076.
5. Start WSJT-X
6. WSJT-X correctly reporting 15m in the dropdown and frequency, Green
light. Everything looks good and signals seen on waterfall.
7. Click monitor button to start decoding, WSJT-X instant change to 10m.
This is a deal breaker for me. I shouldn't have to use WSJT-X to manage
all my VFO changes. I often use the radio for non-WSJT-X purposes and am
often on a different band from the last used WSJT-X. Current;ly, to
avoid unwanted band changes, I need to use the WSJT-X band dropdown
before enabling the monitor button, despite WSJT-X reporting the correct
band, I still need to use the dropdown incase the last used WSJT-X band
is different.
Sorry, this is a backward step from 1.4
de Laurie VK3AMA
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
