Jim's suggestion is a good one. This is exactly what I've been doing from
the start with WriteLog. The terminal window is open all the time on the
second (righthand) monitor, where I also put the BandMap along the left
edge.
I've also thought about the issue Dick raised about stale spots. Currently
we can only set an extinction time for spots. It'd be fantastic to somehow
know the age of a spot.
No desire on my part for displaying the spot's originator. I can either
filter out those I don't want or look in the terminal window.
73,
Barry N1EU
>From: Jim Idelson <k1ir@designet.com>at
>To: WriteLog Reflector <writelog@contesting.com>
>Subject: [WriteLog] Packet spots
To: <writelog@contesting.com>
>Date: Wed, 1 Nov 2000 08:39:09 -0500
>
>Dick,
>
>I handle these issues by keeping the WriteLog Packet Terminal window alive
>all
>the time. This lets me see everything that's going on at the packet source.
>It
>also allows me to 'talk' and 'sh/wwv' any time.
>
>By the way, no one should complain about screen size when running WriteLog.
>You
>can increase available screen area in two ways:
>
>1. Use Windows Multiple Monitor Support. This is easy to do if you are
>using a
>laptop that supports this functionality. You can put your real-time logging
>interface on the main screen and the other information on the secondary
>screen.
>
>2. If you don't want to run multiple monitor support, you can network a
>second
>pc an use the second screen for WL information. This gives you the added
>benefit of a mirrored, redundant log . . . a bit of extra security in the
>event
>you have a problem on the primary logging machine.
>
>73,
>
>Jim K1IR
>
>I noticed a couple of issues when using packet spots this weekend in CQWW
>SSB.
>I normally don't run assisted, so please forgive me if these issues have
>been
>raised before:
>
>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.
>
>2. I could be wrong about this, but I think other contest programs log the
>call
>of the spotting station. This helps when the packet node is accepting spots
>from far away places that might have propagation when we don't. This is
>especially an issue when using Internet clusters (by far, the best way to
>use
>packet spots.) Whether the other programs do it or not, I think it's a good
>idea for WL. It looks like there's plenty of room in the spot window for
>this
>information.
>
>73,
>
>Dick WC1M
>
>--
>WWW: http://www.writelog.com/
>Submissions: writelog@contesting.com
>Administrative requests: writelog-REQUEST@contesting.com
>Problems: owner-writelog@contesting.com
>
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|