All,
I have noticed another issue with Auto Sequence that should be
addressed. Here is a sequence series, copied and pasted from the RX
frequency window, that exemplifies the problem:
181945 7 -0.5 1235 ~ W7RI WA2VCQ EL87 (other calls fm. a previous CQ)
182000 Tx 1236 ~ WA2VCQ W7RI +07 (I respond, auto seq. TX2)
182015 8 -0.5 1235 ~ W7RI WA2VCQ -07 (other stn. responds)
182030 Tx 1236 ~ DE TI3/W7RI R+08 (auto seq. goes to TX3)
182045 11 -0.5 1235 ~ W7RI WA2VCQ RRR (other stn. responds)
(Log QSO dialog box comes up automatically; I clicked OK)
182100 Tx 1236 ~ DE TI3/W7RI 73 (auto seq. goes to TX5)
182115 6 -0.5 1235 ~ TI3/W7RI 73 (other stn. responds)
182130 Tx 1236 ~ WA2VCQ W7RI +06 (auto seq. goes to TX2)
Note that rather than ending the auto sequence after logging, the system
jumped back to TX2 and attempted to continue the auto sequence again
from there, which I had to manually abort.
This problem happens with rather considerable frequency, and if the auto
sequencing sequences from TX2 to TX3, it will ALWAYS happen. Usually,
if the auto sequence jumps from TX2 to TX4 (most often the case), it
will not happen, and the auto sequence will complete normally.
Not sure if it is related to the fact that I am cursed with having to
use a compound call, but maybe...
Regards to all,
Scott Bidstrup
TI3/W7RI
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
