>From Joe’s post yesterday about known bugs:
“1. If a message's first callsign contains only characters 0-9 and A-F it will be interpreted as a hexadecimal number. The message will be transmitted and decoded as if the first callsign were telemetry data; the remaining parts are lost. (Apologies to holders of all such callsigns... we'll fix this very soon.) Jim S. N2ADV From: Jari A [mailto:oh2...@gmail.com] Sent: Wednesday, September 19, 2018 11:21 AM To: WSJT software development Subject: [wsjt-devel] wsjt-X2 Crash report oh2fqv 14.078 af4fa tx at 1496Hz , no locator with the call sign. Tried to double click to the call AF4FA at band activity window, not copied. I type call manually to DX Call field, set manually locator and I made Generate Std Msgs, it move it to TX1-5 fields. This cause WSJT-X2 to transmit AF4FA only, no locator. I tried this 2 full times and at third I interrupt the Tx. I find DC0HD calling CQ ( new call on band color ) DC0HD JO30 1523Hz Double click to hes call and immediate crash with short beep. Windows 7, 64 bit - ts-590sg via CAT control Best regards, : Jari / oh2fqv
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
