Black Michael kirjoitti 18.9.2022 klo 16.59:
I think it's because your callsign is being hashed and the logic is
not allowing for a hashed callsign.
This section removes hash marks from the foxCall -- but not my_callsign.
I had plain call OH1KH (or OH1KJ) there. When my call is hashed it is
done by wsjt-x and as far as I can see it does not affect to this bug.
If wsjt-x generates them for me it should not effect the start of reply
to Fox or ending the qso because then fox is hashed, *not mycall.
*
220918_114600 21.091 Rx FT8 -15 0.8 443*OH1KJ <FH/OK1M> -14 <
that is when wsjt-x should react and start my TX3*
220918_114600 21.091 Rx FT8 -16 0.8 382 <IT9KSS> FH/OK1M RR73
220918_114615 21.091 Tx FT8 0 0.0 2113 <FH/OK1M> OH1KJ KP01
*<how ever it does not*
220918_114619 21.091 Tx FT8 0 0.0 2113 <FH/OK1M> OH1KJ R-15 <
here clicked rx line to get TX3 running
So it is not so easy as you say.
I have found the part of code where FOX call is srtipped from "< >". But
this Fox call has still slash after stripping.
How ever it looks that at the part of stripping "< >" does not look
slash existence there.
Could it be in somewhere else than between mainwindow.ccp lines 3930 -
3960 that makes TX3 start / stop fail?
--
Saku
OH1KH
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
