That's basically it. At one point I thought I saw it clobber an
existing log entry by changing the time/date and band but when I
tried to reproduce that, I couldn't. Perhaps it was caused by the
failure to unfilter the log. We'll test some more with the new
version.
73, Rich - W3ZJ
toggle quoted message
Show quoted text
-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, April 07, 2001 1:23 AM
To: dxlab@...
Subject: [dxlab] DXKeeper 1.2.1 is available
I noted two QSO Capture window defects in the scenario
outlined below:
#19: clicking the Log button failed to unfilter the log
#20: the recorded QSO start time is bogus
Was there something else?
Both above the above defects are corrected in DXKeeper
1.2.1; when no QSO
start time is established (by clicking the Start
button), the QSO start time
is set to the QSO end time.
If you've already installed DXKeeper 1.1.1 or later,
you can upgrade to
version 1.2.1 by downloading and then running
--
your online help will
be updated by this process.
73,
Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Friday, April 06, 2001 18:37 PM
To: Dxlab
Subject: [dxlab] DXKeeper 1.2.0
Dave,
Try the following. In the capture window, enter a
callsign of a
station that "is" in your log, press enter. All looks
fine so far,
does the lookup - great. Now click log to log it.
Whacky!! If you
need more detail let me know, but I think you'll see it.
-----
73, Rich - W3ZJ
www.w3zj.com
Yahoo! Groups Sponsor
To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.
To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...
Your use of Yahoo! Groups is subject to
