>One more question: you cannot preview the entire QTC block prior
to
>sending it. If you happen to start sending QTC to DL0BD for
instance and
>one of the lines in that QTC block is the info about QSO with
DL0BD the
>program stops sending all the following lines. It looks like you
>promised to send 10 QTC to your contact in the beginning but
then
>changed you mind and sent only 3 or 4. Yet the number that you
have sent
>in the beginning says something like 32/10. I know, it is
probably
>difficult to overcome but what about letting the operator to
preview the
>QTC and use the cursor to move around the QTC screen so that
unwanted
>line can be marked "do not send" or "repeat this line again" and
the
>header is formed only after previewing and marking.
Good point, Igor.
When I read it in the rules DURING the contest (one of these days
I am going to be prepared for a contest!), I wasn't sure if that
had happened during any of the QTC's I had sent out earlier. I
never did see that happen. But, conceivably it could. Maybe the
software can be written to recognize that the QTC's are being
sent to a station whose call is in that group and skip over that
QTC to save it for transmission to another station later.
There's nothing in the rules saying the QTC's have to be sent in
any particular order...That way, it would be invisible to the
both operators and not require any special manipulation by the
sending operator. .
Also, I felt guilty as heck when I had to tell a Euro asking QTC?
that I was QRU, when, in fact, I had five QSO's right in front of
me. I realize the situation, but still felt a bit badly about
the 'lie.' Maybe there should be a guilt multiplier in this
contest!
73,
dale, kg5u
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|