On 13/12/2018 18:36, Al Pawlowski wrote:
Can not remember the specific thing I was doing when it bugged me last
- probably experimenting with virtual audio, and radio, connection
changes. In any case, it seems to me that locking the program is
overkill for the triggering condition.
Al Pawlowski, K6AVP
Los Osos, CA USA
Hi Al,
you are only seeing the end of a story when that rig control error pops
up. Hamlib makes several retries when an unexpected response, or lack of
response, happens, WSJT-X also retries several times before we give up
and ask the user for help. If you have configured WSJT-X to use CAT
control of a rig then it expects to be able to do just that, the options
are retry, report the full error, fix it, or exit. What is this locking
you are referring to? Do you want to be able to carry on with
non-functional CAT control, if so then you will have to use a different
application!
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
