Re: [wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

2017-11-25 Thread Bill Somerville
On 26/11/2017 02:34, carc...@gmail.com wrote: So, on to Mac OS 10.13.1: When I try and run WSJT-X the "splash screen" briefly appears then get "Shared Memory Error", unable to create shared memory segment. Followed by "Fatal error, shared memory error", yes, related. OM, please read the

Re: [wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

2017-11-25 Thread Bill Somerville
Hi OM, some comments in line below. On 26/11/2017 02:34, carc...@gmail.com wrote: Today I tried 1.8.0 release. After a few transmits the waterfall window would freeze. Closing the program via the "X" in the upper right hand corner seemed to work, but upon trying to start up WSJT-X again I'd

[wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

2017-11-25 Thread carcarx
I changed QTHs and am now in a condo, so it's rare for me to get my multiband vertical up on its tripod to operate. Earlier in the summer I'd used 1.8.0 RC1 and operated FT8 enough to get my sig spotted. Today I tried 1.8.0 release. After a few transmits the waterfall window would freeze.

Re: [wsjt-devel] Split frequency logging

2017-11-25 Thread Dan Malcolm
Very cool Mike. Thanks __ Dan – K4SHQ From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Saturday, November 25, 2017 6:55 AM To: WSJT software development Cc: Black Michael Subject: Re: [wsjt-devel]

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

Re: [wsjt-devel] Split frequency logging

2017-11-25 Thread Black Michael via wsjt-devel
That change is in beta testing for JTAlert right now.  And it's working de Mke W9MDB On Saturday, November 25, 2017, 5:48:59 AM CST, Dan Malcolm wrote: Claude et al, Exactly.  That's why this is a development question.  The ADIF fields are there, and

Re: [wsjt-devel] Split frequency logging

2017-11-25 Thread Dan Malcolm
Claude et al, Exactly. That's why this is a development question. The ADIF fields are there, and apparently not being used, or I missed a setting somewhere. I agree in principle with Karl. Too much automation is not a good thing. But as long as frequency is being logged, it should be done