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
the option is off by default which I think you will want to leave as
is. The option being on is equivalent to the current v1.4/v1.5
implementation.
You may also wish to allow monitor to come on at startup as this will
not qsy the rig if the above option is unchecked.
Hopefully I have got the implementation right but it may have
interfered with correct CAT control as there is still a rather over
complex UI logic which really needs cleaning up :(
Give it a try and tell me what you think?
73
Bill
G4WJS.
Bill,
Thanks. Works well.
I can now start with monitor enabled, which in the past was what I
always used.
It was only the recent changes requiring me to start WSJt-X with monitor
off was the genesis of the "unwanted Band changes when enabling monitor"
I was experiencing.
This test version works as I would expect most users would prefer,
WSJT-X starting with monitor on and no unwanted band changes if monitor
was off and the user turned it on.
de Laurie VK3AMA
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel