On 31 Jan 2019 at 6:14, Gene H wrote:
> Yes, we have noticed this routinely with compound callsigns. It likely
> is related to the complexity of compound callsigns and lack of number of
> bits to send all information. I noticed if you hover your mouse over the
> *Settings > General* tab on top
ceived report not being logged
From: "Martin Davies G0HDB" <marting0...@gmail.com>
Date: Thu, January 31, 2019 6:44 am
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Cc: bil...@classdesign.com
Hello all, I'm running WSJT-X v2.0.0 r784f75 on a PC with 3
Yes, we have noticed this routinely with compound callsigns. It likely
is related to the complexity of compound callsigns and lack of number of
bits to send all information. I noticed if you hover your mouse over the
*Settings > General* tab on top of the *Station Details* "Message
generation f
Hello all, I'm running WSJT-X v2.0.0 r784f75 on a PC with 32-bit Win 7 Pro.
I've discovered that for a few of my recent QSOs the received-report field
didn't get populated
when the QSO was logged. I first spotted this when I looked at my QSOs as
picked up via
UDP by the Logger32 app, and then
