<div>Hi Tono and others...this is the best sounding solution I have heard yet...</div><div> </div><div>de Rick NQ4I<br><br></div><div class="gmail_quote">On Tue, May 29, 2012 at 7:41 AM, Wolfgang -DK9VZ- <span dir="ltr"><<a href="mailto:ws@dk9vz.com" target="_blank">ws@dk9vz.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">Hey Tönno<br>
<br>
yes you're right, I didn´t consider that there is another mode called SSB,<br>
which I normally don´t use and don´t like ;-))<br>
<br>
So your proposal to increment SN only the callsign fileld is empty<br>
would be a very good solution in my view also.<br>
<br>
It could lead to having sent the same number twice, but when both QSOs<br>
are logged with that same number and could be cross checked it wouldn´t be a problem.<br>
A gap (a number without an assigned QSO) would not appear.<br>
<br>
When can we have it? ;-))<br>
<br>
/*73 de*/<br>
/*Wolfgang DK9VZ*/<br>
<a href="mailto:ws@dk9vz.com" target="_blank">ws@dk9vz.com</a> <mailto:<a href="mailto:ws@dk9vz.com" target="_blank">ws@dk9vz.com</a>><br>
<br>
<br>
Am 29.05.2012 13:25, schrieb Tõnno Vähk:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div><div class="h5">
<br>
I see a very interesting and needed discussion here. We just completed another MS operation in WPX which now has one numbering sequence only and running with 5 stations you need all them to coordinate numbers. It is a mess as often the number is stolen from the RUN station or another station after it has given it out but before he has pressed Enter and then the wrong sent number gets into the log. We do use $NEXTSERIAL, etc... But a lot of human mistakes happen. And unfortunately it is the innocent caller who gets punished as he will lose the QSO because “wrongly copied“ exchange.<br>
<br>
I have seen the opinion of WT guys and solutions proposed and arguments presented to protect the current system. Well, obviously a critical mass of people have huge problems with this thing and we would need at least some optional solution. It is clear that none of the contest organizers require perfect line of numbers and what is important is that the numbers match in logs. So preserving a clean sequence is not an argument.<br>
<br>
Reserving the number somehow when it is sent does not quite work as in SSB it won’t work and even in CW some guys send with paddle, etc.. Bob’s idea abut the program checking what was sent and logging it is interesting but again not universal.<br>
<br>
It seems to me that the best option is to have a following tickable option in WT:<br>
<br>
ONLY INCREMENT SERIAL NUMBER WHEN CALLSIGN FIELD IS EMPTY<br>
<br>
That’s it. Let the station who has something on the callsign field keep the number. This way it can never happen that you log a different number from what is sent! If the QSO does not happen and you clear the callsign field the number gets immidiately synchronized again! Can someone point out when this solution would not work?<br>
<br>
If only it would not require rewriting the whole code of the program! Does it??<br>
<br>
73<br>
<br>
Es5tv<br>
<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
Support mailing list<br>
<a href="mailto:support@win-test.com" target="_blank">support@win-test.com</a><br>
<a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-<u></u>bin/mailman/listinfo/support</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Support mailing list<br>
<a href="mailto:support@win-test.com" target="_blank">support@win-test.com</a><br>
<a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-<u></u>bin/mailman/listinfo/support</a><br>
</blockquote></div><br>