[Dx4win] Version 7.01?

[Jim Reisert AD1C]

--- "Marc Wullaert (ON4MA)" <marc.wullaert3 at pandora.be> wrote:

> I reported and other also about the states bug but got no response.
> example
> if you have K1ZM in your log and his  states is MA
> if you work K1ZMA he will not clear the states flag will keep MA or you have
> to
> manually change  it !Not diffucult but when running a pile up whit a special
> pfx

Hi Marc,

I think I can reproduce this bug in 7.01.  If this is not the bug let me know:

I type in the callsign W1JR and the state is NH (from a previous QSO).  I have
not saved the QSO yet.  Then I realize that I got the call wrong (it's really
W1JRK), so I tab into (or click inside) the callsign field and add a "K" at the
end.  The state field remains NH.

This problem does NOT occur when "Callsign Update" is enabled in the QSO
prefereces.  For those of you who have never tried "Callsign Update" try it and
see.  The logbook information automatically updates for each character of the
call you enter, intead of waiting until you tab/click out out of the callsign
field.  I learned about it at Dayton.  It's pretty neat.

I agree that this is a problem.  However, imagine a fix for the above, and what
can happen:

I start to log W1ABC (new call in my log).  I type in the state as RI.  Then I
realize the call should have been W1BAC.  I correct the call and the state
disappears!  If you forget to enter it again, the information is lost.

I think fixing the problem is the right thing to do, since it's better to have
NO information than INCORRECT information.  We will have to see what Paul says.

73 - Jim AD1C


--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, <jjreisert at alum.mit.edu>, http://www.ad1c.us