Rather than consume real estate on the screen displaying the time of a packet
spot, I suggest using the one-character "clock"
symbols which are available in the WingDings font. A "noon" clock is fresh
meat. A "one o'clock" clock is a 5 minute old spot. A
"two o'clock" clock is a 10 minute old spot. And so forth. I think no one is
interested in spots that are more than 55 minutes
old.
The clock wingding could also be appended to the callsign in the bandmap to
indicate age on the bandmap.
-- Eric K3NA
-----Original Message-----
From: owner-writelog@contesting.com
[mailto:owner-writelog@contesting.com]On Behalf Of Kurszewski
Chad-WCK005
Sent: 2000 November 1 Wed 19:32
To: writelog@contesting.com
Subject: RE: [WriteLog] Packet spots
> 1. In other contest programs, the time of each packet spot appears in the
> spot window. This allows the op to quickly identify the spots that are
> getting a little stale. This would be a good addition for WL.
>
Keeping the packet terminal open to see the spotter and time of
spot isn't the solution. On telnet, these spots just fly by,
and it's difficult to match up the mult window spot with the
packet window spot, especially if you wait more than a minute
to work the spot.
We experienced a time during the contest where the spots we were
getting were 1 to TWO hours old. (Must have been a long delayed loop.)
One couldn't tell in the "Packet Spots" window that these spots were
that old.
It certainly would be an EXCELLENT addition to include the time
of the spot (not the arrival time, but the timestamp of the spot)
in the "Packet Spots" window so one could quickly delete the ancient
spots.
Chad WE9V
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|