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 > Date: Thu, 13 Dec 2018 17:59:36 +0000 > From: Bill Somerville <g4...@classdesign.com <mailto:g4...@classdesign.com>> > To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > Subject: Re: [wsjt-devel] Rig Connection Warning Window Suggestion > Message-ID: <8d36dcd9-87f3-eaf0-553f-4d4db095d...@classdesign.com > <mailto:8d36dcd9-87f3-eaf0-553f-4d4db095d...@classdesign.com>> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 13/12/2018 17:52, Al Pawlowski wrote: >> I would like to see the Rig Connection Warning window functionality >> changed so that it can be closed/dismissed without closing the whole >> program if a rig connection problem is not fixed. At times, the >> current ?shutdown or lockup only? operation can be pretty annoying. >> >> >> Al Pawlowski, K6AVP >> Los Osos, CA USA > > Hi Al, > > that's what the "Ok" button is for, it takes you back to the setting > page where you can fix the problem. What else would you want to do? > > 73 > Bill
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
