Re: [wsjt-devel] Call change while logging

2017-11-26 Thread Brian Moran
I haven't seen the callsign field change but HAVE seen the report field change to the value for the next caller. Not sure of a repro case, however I imagine a careful exam of all.txt could yield examples. Sent via iPhone > On Nov 26, 2017, at 2:24 PM, Bill Somerville

Re: [wsjt-devel] Call change while logging

2017-11-26 Thread Bill Somerville
On 26/11/2017 20:50, Scott Bidstrup wrote: It would be preferable, I think, to simply allow the changing of the DX call in auto sequence, but NOT change the data that is in the dialog box that is going to go to the log file when the log dialog box is open and then OKed.  This would solve the

Re: [wsjt-devel] Call change while logging

2017-11-26 Thread Scott Bidstrup
It would be preferable, I think, to simply allow the changing of the DX call in auto sequence, but NOT change the data that is in the dialog box that is going to go to the log file when the log dialog box is open and then OKed. This would solve the problem, but not cause a problem with the

Re: [wsjt-devel] Call change while logging

2017-11-26 Thread Bill Somerville
On 26/11/2017 20:08, Scott Bidstrup wrote: On 26/11/2017 01:04 p.m., Rich - K1HTV wrote: Disabling the changing of the DX call while the logging box is open would prevent the problems now being experienced for those that don't act fast enough to log the previous QSO. I've had this happen to

Re: [wsjt-devel] Call change while logging

2017-11-26 Thread Scott Bidstrup
On 26/11/2017 01:04 p.m., Rich - K1HTV wrote: Disabling the changing of the DX call while the logging box is open would prevent the problems now being experienced for those that don't act fast enough to log the previous QSO. I've had this happen to me, too. It would be preferable, I think,

Re: [wsjt-devel] Call change while logging

2017-11-26 Thread Rich - K1HTV
25 Nov 2017 13:17:13 + (UTC) From: Black Michael <mdblac...@yahoo.com> To: WSJT Software Development <wsjt-devel@lists.sourceforge.net> Subject: [wsjt-devel] Call change while logging Message-ID: <150424686.2916460.1511615833...@mail.yahoo.com> Content-Type: text/plain; ch

Re: [wsjt-devel] Call change while logging

2017-11-25 Thread Bill Somerville
On 25/11/2017 13:17, Black Michael via wsjt-devel wrote: There's a problem logging with JTAlert (and perhaps other apps too) if you leave the logging dialog box open and change the active call sign. JTAlert maintains the additional logging info by the active call signlike countryso

[wsjt-devel] Call change while logging

2017-11-25 Thread Black Michael via wsjt-devel
There's a problem logging with JTAlert (and perhaps other apps too) if you leave the logging dialog box open and change the active call sign. JTAlert maintains the additional logging info by the active call signlike countryso you may end up logging the wrong country. There's a potential