On 27/10/2018 05:48, Laurie, VK3AMA wrote:
Observed in v 2.0.0 rc2 & rc3
The Message field in the UDP Decode packet (#2) has an incorrect
message length value (short by 2) when the message contains a compound
callsign. Looks like the message length value is not adjusted to
account for the 2 additional [<>] characters.
Initially observed in JTAlert during debugging and confirmed by WSJT-X
Message Aggregator.
WSJT-X correctly displays the full message.
Hi Laurie,
thanks for the issue report. This one is non-trivial to fix. It is not
specifically the '<' and '>' characters that are causing the issue, it
is simply that the decoded message lengths have increased and are
getting truncated. The problem is that the codec interfaces have added
extra non decode text to the end of some decodes, this is mainly due to
a rather clunky design that makes it hard to pass extra information back
to the UI and it is tricky to generically separate the actual decode
from appended information. Incidentally, this also why Hound mode
decodes are not delivered as UDP messages since they too can be longer
than the original length limit.
I will see what I can do within the current framework but I fear that
this may only be fully solved by completing a long-standing refactoring
to combine the jt9 and wsjtx executables. That refactoring is too big to
make it into v2.0.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
