] WSJT-X 1.5 Dev unwanted Band Changes when
using Monitor button
On 22/02/2015 23:52, Laurie VK3AMA wrote:
Hi Laurie,
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
On 23/02/2015 12:04 PM, Bill Somerville wrote:
6. WSJT-X correctly reporting 15m in the dropdown and frequency,
Green light. Everything looks good and signals seen on waterfall.
I cannot reproduce step (6), with Monitor off the waterfall is disabled
My mistake. I have two other
On 23/02/2015 1:05 PM, Bill Somerville wrote:
Hi Laurie,
just as a trial, the following has a new option that causes WSJT-X to
return to the last monitored frequency when monitor is enabled:
https://dl.dropboxusercontent.com/u/4192709/wsjtx-1.5.0-devel-win32-r4986-moni-last-used-option.exe
On 23/02/2015 1:05 PM, Bill Somerville wrote:
Hi Laurie,
just as a trial, the following has a new option that causes WSJT-X to
return to the last monitored frequency when monitor is enabled:
https://dl.dropboxusercontent.com/u/4192709/wsjtx-1.5.0-devel-win32-r4986-moni-last-used-option.exe
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
On 22/02/2015 23:52, Laurie VK3AMA wrote:
Hi Laurie,
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
A briefer description of the broken behaviour...
WSJT-X at startup correctly reports the frequency of the radio VFO and
the Band dropdown changes correctly to match the frequency. But, if that
is not the last used WSJT-X band, enabling monitor forces the band change.
de Laurie VK3AMA
