Bob --
I actually prefer the slide rule format because it shows graphically empty
spaces in the band (i.e., potential running
frequencies). If you set the kHz-per-pixel value to an appropriate size for CW
or SSB, you can actually see quite a lot of the
band. I set my bandmap windows to occupy the entire vertical space of the
window, one on each side (left radio and right radio).
-- Eric K3NA
-----Original Message-----
From: writelog-admin@contesting.com
[mailto:writelog-admin@contesting.com]On Behalf Of W3YY@aol.com
Sent: 2002 October 16 Wed 19:25
To: writelog@contesting.com
Subject: [WriteLog] Bandmap Scrolling - How About a Tabular Display?
First, let me say I think WriteLog is absolutely the best contest logging
program, or I wouldn't be using it. The Windows format is great for packing
lots of information on the screen in a very flexible way. To me it beats all
the DOS contest programs, hands down.
That said, one of the things that I would like in WriteLog would be a bandmap
similar to TR Log, i.e., a simple tabular listing of call signs and
frequencies across the entire band. When did slide rule dials go out of
existence? With the NC-300? Why are we displaying this information in this
antiquated way? I program, and I'm impressed with the effort that must have
gone into this display - my kudos to the programmer, but I think there are
more efficient, albeit not pretty, ways to display this information. Windows
is great for a tabular listing. You could change the font size to probably
show at any time all the recent spots in even the most active contest in any
window. Or, just resize the window. It's perfect.
Again, I hate to suggest changes because I really think WriteLog is a
marvelous program and I appreciate the incredible effort and skill that has
gone into creating it. In any case, I truly mean this as positive feedback,
and I hope it is taken that way.
73, Bob - W3YY
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
|