Yes it was a different mode before but the highlight by mode is not checked so shouldn't it just consider it a new call or not a new call without regard to the mode? Perhaps I don't understand the logic yet ... can you explain it a little better or do you think it not working yet?
I had already tried both the Win64 OpenSSL v1.0.2p Light and Win64 OpenSSL v1.1.1 Light but the confusion was the 32 bit version suggested in the pdf I thought that was a mistake in the manual! Confusing because people will try to get a 64 bit version if they have that OS, so now I got the right one and it works! Mike N5INP On Tue, Nov 13, 2018 at 2:25 PM Bill Somerville <g4...@classdesign.com> wrote: > Hi Mike, > > comments below. > > On 13/11/2018 20:13, Mike wrote: > > The "New Call" color annunciation is triggering falsely. It's claiming > N2ADV when he's calling CQ on 20 meters today is a new call, but the > contact is definitely still in the file as a contact from 2014. > > Please double check the entry in your WSJT-X ADIF log file that you think > means this is not a new caller. For example is the mode different? You have > an option to highlight new ones by mode if you wish, it is a new check box > on the "Settings->Colors" panel. > > > Also still getting the "Error loading LoTW Users data" error when starting > the program. > > Have you taken note of the section headed "LoTW Download Errors" in the > v2.0 Quick Start Guide: > https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf ? > > 73 > Bill > G4WJS. > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
