I don't know if its the commas in the text, or any text,
but I decided to watch more closely for a while and see if
I can see a stronger connection.
1. Sure enough, there was a packet spot in the spot window
for TZ9A that had no time. When I switched to look at
the packet window, I found this entry:
DX DE KC2NMZ TZ9A 18150.0 bands great again Chris 59 plu2153Z
with the text running over where the Prefix should be,
and sure enough, that spot had no time value.
So I wrote the above info down for this email, and
then, just to be sure, went back to the spot window,
and now TZ9A 2154Z is shown, and it now has a timestamp!!
But, going back to the packet window, there is a new post
DX DE W2QN TZ9A 18150.0 TZ 2154Z CT
containing a valid prefix and state, and that second post caused
the time value to be added before my very own eyes.
2. But two later posts, now with text and with a country prefix,
but without the STATE of the poster both showed up without time
stamps in two posts, because the callsign was corrected:
DX DE KC2NMZ 9H0AL 10107.0 text------- 9H 2159Z
DX DE KC2NMZ 9H1AL 10108.0 text-------------- 9H 2203Z
Thus I conclude that WriteLog does not populate the time value
in the spot window if there is no STATE after the timestamp in
the packet spot.
Anyone else looking at these 17 minute old spots see the same thing?
73
Barry, W5GN
-----Original Message-----
From: Jim Reisert AD1C [mailto:jjreisert@alum.mit.edu]
Sent: Monday, September 19, 2005 11:56 AM
To: barry@mxg.com
Subject: Re: [WriteLog] Time value is missing in some spots
I wonder if it was the comma inside the comment...
--- Barry Merrill <barry@mxg.com> wrote:
> I posted this a few weeks ago, updated to 10.55D, and thought the
> problem was fixed, but I continue to experience spots with no time
> value, and all of the cases have no "country" nor "state"
> before and after the time in the packet window. For example, this
> spot this past weekend, had this entry in the packet window:
>
>
> DX DE KC2NMZ: 28450.0 VP6SL Light, light ... 2019Z
>
> i. e., there was no country prefix before the time, and there was not
> state after the time,
>
> but in the packet spot window, the spot had no time value shown.
>
> However, WriteLog must have kept the time internally; checking the
> sort by asimuth box reordered the spots by azimuth, but then
> unchecking it to put them back in time order, that spot WAS put back
> in the correct place, based on the before and after timestamps of the
> adjacent spots in the spot window.
>
> Am I the only one experiencing this problem, or just the only one
> observing the problem, because who uses the azmiuth checkbox, as that
> is when knowing the time value is most important.
>
> If someone else can verify what I'm seeing, then perhaps Wayne will be
> able to diagnose and correct the occasional missing times in the
> packet spot window.
>
> 73
>
> Barry, W5GN
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA
+978-251-9933, <jjreisert@alum.mit.edu>, http://www.ad1c.us
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|