WriteLog
[Top] [All Lists]

[WriteLog] 7QP Module

To: <writelog@contesting.com>
Subject: [WriteLog] 7QP Module
From: "\(K7ZO\) Scott Tuthill" <k7zo@cableone.net>
Date: Thu, 8 May 2014 08:07:45 -0600
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
Jim and Rod:

Yes -- there is much wrong with the 7QP module for WriteLog. Other various issues that I have seen in past years are;
* It does not score correctly -- it does not include the DX mults
* It does not support digital operation
* And most importantly, it is a performance dog. As the log grows the PC quickly bogs down. CW sending becomes erratic, etc. This can be somewhat worked around by turning off automatic scoring and duping, but it is a real problem.

These issues have existed for several years and requests have been made to address them with no change. The 7QP is a complex contest from a module creation process and, as a QSO party, it is not a major event. So, I imagine the Wlog team prioritizes their time elsewhere.

My recommendation, and what we did at NK7U, is to move to N1MM for 7QP. It works much better.

The Writelog Packet Terminal issue has existed for a long time and is not specific to 7QP. If you need to close it just use the Task Manager.

Scott/K7ZO


Message: 2
Date: Tue, 06 May 2014 17:11:20 -0700
From: Jim Forsyth <jim@af6o.com>
To: writelog@contesting.com
Subject: Re: [WriteLog] 7QP Module
Message-ID: <53697A28.5020202@af6o.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I found WL to be wholly inadequate for 7QP.

Upon entering a call into the log window it would prefill the exchange
with the *first *exchange that had been entered for that station. What
you need is the *last *exchange entered (for that band/mode) so that you
can see (in the case of a mobile) if he has moved on to another county.

When entering two counties for a station it would often report,
incorrectly, that the second one was invalid and would delete it. Hence
necessitating entering two QSOs to get both counties logged.

There was no indication in the log when a dupe was logged.

What is "Check Call"?

Jim, AF6O


On 5/6/2014 4:06 PM, Rod via WriteLog wrote:

While operating a FT-1000MP to MicroHam Keyer II in the 7QP, the WL module
began faulting.  Thus closing WL to perform a short  reset was needed to
clear the lockup:

"Check Call" did not show previous contacts. It did not highlight that a
potential call was a dupe.

   Did not accurately count the number of contacts on the "Band  Summary"
window.

Did anyone else have module problems?

While I am at it one constant fault is the inability to move from  one
module to another [ala ARI to 7QP] without a freeze. It happens with most modules requiring a form to be filled out when first used. You can close WL down for a reset but the WL "Writelog Packet Terminal" will not close. Thus
a Ctrl-Alt-delete sequence to clear it.

73

Rod W7OM
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/



_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

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