Bob, TNX for your reply email.
I am seeing 2 problems...
1) Are you using the MAP window feature?
I am connected to a spotting network. Spots appear in the MAP as expected.
When I click on a station CALL (on the map), and ENTER it into the log, then
CALL should change color from (the not worked color - YELLOW?) to DARK BLUE
(worked). I am not seeing this happen.
ALSO... Dave, NC6P, is describing another problem where the RCVD field only
is displaying 4 characters. I am also seeing this problem. Here is what I
can do to repeat the error... it appears to be a DUPE QSO related problem.
Say I work K7K on 40m/cw in AZMCP. This appears correctly in my log
window.
Later I find K7K again on 40m/cw and put his call in the CALL window
(this is a DUPE QSO
situation). WL will populate the RCVD field with a truncated 4-character
QTH (AZMC) and
call it a NEW STATION. I am unable to add the missing 'P' character at
in the RCVD field
(I can type a 'P', but when I leave the RCVD field, it reverts back to a
4-character QTH and
I get the UNKNOWN MULT error message).
On the other hand.... suppose K7K is now in a different county. (i.e. it
is no longer the DUPE
QSO situation). I still have this erroneous 4-character QTH in the RCVD
field. I can back
it out and add the new county QTH and it will be accepted as a new and
valid QSO.
I think the program might flow better if it did NOT populate the county QTH
when I come across the
DUPE CALL situation. The program should only detect a DUPE QSO when it has
the QTH field(s).
So, are you able to repeat this scenario and get the 4-character QTH result?
Jerry, k6iii
Grass Valley, CA
================================================
Message: 1
Date: Fri, 9 May 2008 16:15:04 -0700
From: Bob Jensen - aa7fk <aa7fk@hotmail.com>
Subject: Re: [WriteLog] WriteLog 7QP Dupe problem, 10.62H
To: <writelog@contesting.com>
Dave & Jerry,
I operated 7QP with ver 10.63H and it handled dupes correctly, announcing in
red when a dupe was entered in the callsign box .. and I did log one dupe
and in that case it identified it with the red D in the log, just as it's
suppose to. So 10.63H handled dupes in 7QP OK for me.
73
Bob AA7FK> Date: Wed, 7 May 2008 21:23:50 -0700> From: jerry.bliss@gmail.com>
To: writelog@contesting.com> CC: ahab@sonic.net> Subject: [WriteLog]
WriteLog 7QP Dupe problem, 10.62H> > Yes, Dave, I am seeing it also. I am
running WL10.62H> Darn annoying. Hope it gets fixed before 2009!> de Jerry,
k6iii> ===========================> Hello to all. Has anyone else tried the
7QP module yet? I was giving it a> try, changing bands and making dummy QSOs
to see if it works. I put in dupe> qsos and it doesn't flag it as a dupe,
but puts a four letter exchange into> the "RCVD" field. So, it kind of works
if you know what to look for. I am> running ver 10.62H, has anyone else had
this bug? Will an earlier version> run correctly? Thanks for your help,
Dave, NC6P.>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|