WriteLog
[Top] [All Lists]

[WriteLog] Operational Characteristics of WL on CW

To: <writelog@contesting.com>
Subject: [WriteLog] Operational Characteristics of WL on CW
From: jimsmith@shaw.ca (Jim Smith)
Date: Fri, 06 Dec 2002 00:06:11 -0800
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



<Prev in Thread] Current Thread [Next in Thread>