[WriteLog] Operational Characteristics of WL on CW

[Eric Scace K3NA]

Hi Jim --

   I can't figure out where the "extra keystroke" is that you are discussing.  (You must understand that I have never used TRlog.)
Assuming one doesn't make any typing mistakes, the sequence for running is:
1. push a key to call CQ.  (You can configure WL in different ways, depending on which key you want to push.)
2. hear a station reply and type in his call.
3. push a key to send the call & exchange.
4. hear the station's exchange and type it in, using Space or Tab to move from the callsign field to the various exchange fields.
5. push a key to send the TU message AND simultaneously save the QSO in the log.

   Similarly, for S&P:
1. hear a station, type in his call, hit space to check for dupe (and get ready to log the exchange).
2. push a key to call him.
3. hear the station's exchange and type it in, using Space or Tab to continue moving around the various exchange fields.
4. when you are satisfied that all the data, including the call, has been entered correctly and the station has completed the QSO
with you, push a key to save the QSO in the log.

   What am I missing here?

   You suggested a message "Do you want to log the existing call?" if one types in the callsign field when there is an apparently
valid call & exchange in the QSO Entry form.  I do not see how that can work.  How does the software distinguish between when one is
typing in the callsign field to correct an entry... and typing to make a new QSO without having completed the previous QSO?

-- Eric K3NA

-----Original Message-----
From: writelog-admin@contesting.com
[mailto:writelog-admin@contesting.com]On Behalf Of Jim Smith
Sent: 2002 December 6 Fri 02:06
To: writelog@contesting.com
Subject: Re: [WriteLog] Operational Characteristics of WL on CW


Well, thanks everyone for your time and trouble, both here and direct.
 It's going to take me a little while to digest all this.

One thing that seems to come through is that WL users have learned to
always use that one more keystroke that seems to be needed to log the Q
in S&P.  As I only use WL for RTTY and TR for everything else, and as I
might enter say, 3 RTTY contests in a year and about 25-30 CW and SSB
ones, it's hard for me to remember that extra stroke and I lose Qs, lots
of them.  This, of course, means that some of you also lose Qs you made
with me.  In one contest I lost many Qs in a row before realizing that
they weren't being logged.  How did I notice?  I was S&Ping along making
Qs at a reasonable clip when I saw that the rate meter said zero.  You
can appreciate that this made me "unhappy".

I've had a few folks tell me privately that they have the same problem.
 TR users all, I suppose.

A possible "fix" that occurs to me goes as follows:

There's a call in the call field and a valid exchange in the exchange
fields.
I enter a new call in the call field.
WL says, "Do you want to log the existing call? Y/N"
I respond appropriately.
If Y, WL logs the last Q, displays the new call and waits for the
exchange info.
If N, WL doesn't log the last Q because I'm telling WL that it wasn't a Q.

This would stop me from forgetting to put you in the log which will make
both of us very happy.  Not only that, the constant nagging would
eventually make me remember to make that 3rd keystroke.

Would this drive the rest of you nuts?  Presumably if you have already
logged the Q this message wouldn't come up so it wouldn't slow you down
at all.

Maybe see you in TARA Sprint.

73 de Jim (the untrainable) Smith    VE7FO


_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog