<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 5/28/2012 8:02 PM, Bob Wilson, N6TV wrote:
<blockquote
cite="mid:CAOmNKG+BzH14QXWbn7muyCboFp8QQjDqbA8KTfrJ2QXajMmLVw@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Mon, May 28, 2012 at 3:34 PM, Rick
Dougherty NQ4I <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:nq4i@contesting.com" target="_blank">nq4i@contesting.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hi All...used WT in WPX CW and it worked really good...it
does however have a major issue...when it comes to numbers
sent and numbers in the que it does not do the job.</div>
<div> In a Multi Multi when both stations are very active..its
the toss of the dice to see who gets what number...the RUN
station send a number only to find out that the MULT station
has already given the number to another..and it will send
the WRONG number to the RUN stations qso...[...].it is time
to </div>
<div>step up to the plate and fix the problem.....some sore of
fix is needed...I am hoping that by the time we do WPX next
year that this is not an issue...</div>
<div> </div>
<div>Thank You</div>
<div> </div>
<div>de Rick NQ4I</div>
</blockquote>
<br>
<div><br>
</div>
<div>I think the easiest way to work around this problem in
Win-Test is to simply provide a better method than the
cumbersome "Edit | Edit sent serial no." dialog, so that you
can quickly change the QSO no. logged to the QSO no. that was
actually sent, whenever a timing glitch causes them not to
match.</div>
</div>
</blockquote>
<br>
<blockquote
cite="mid:CAOmNKG+BzH14QXWbn7muyCboFp8QQjDqbA8KTfrJ2QXajMmLVw@mail.gmail.com"
type="cite">
<div class="gmail_quote">[...]
<div><br>
</div>
<div>If you could just edit the SENT serial no. column as easily
as you can edit the RST SENT column, this problem wouldn't be
very cumbersome to deal with. [ ...]<br>
</div>
<div>73,</div>
<div>Bob, N6TV</div>
</div>
<br>
</blockquote>
Hi Bob:<br>
<br>
I strongly disagree. We are doing interleaving of QSOs at very high
rates with hardware interlocks. The sequence of working a QSO by
the run (or S&P) station needs to be exactly the same whether
there is an interleaved QSO or not. If it's done smoothly, the run
operator may not even really be aware that there was an interleaved
QSO!<br>
<br>
Your proposed solution interferes with the rhythm of the run
operator. And, I still think that tired operators won't do this
well at 5:00AM!<br>
<br>
Also, any solution needs to use a minimum number of keystrokes, say
"enter" "enter". <br>
<br>
I have reluctantly quit using Wintest because of this issue. If you
recall, I raised it last year after WPX SSB and suggested the
possibility of just freezing the GUI to make sure that the number
that was sent is what was logged.<br>
<br>
73,<br>
<br>
Mark, KD4D<br>
</body>
</html>