On Wed, 2003-06-18 at 11:10, Tree wrote:
> Great. This certainly isn't one of TR's long suits. Not sure it ever will
> be unless I change the .DAT log format (something I have not done for 12
> years now).
How about modifying POST to scan the .DAT file for
specifically-formatted comments and changing the "my grid" value
appropriately?
So the "my grid" field would be filled by the value of the MY GRID=
logcfg.dat variable *until* a comment like ";now EN62" appears in the
.DAT file at which time the field would be filled with EN62.
Eventually this could also be used by the main TR program to keep track
of which grids you've operated from. (which for a rover contributes to
your multiplier)
On a very vaguely related subject...
POST writes the entry category as "ROVER ALL LOW SINGLE-OP" or something
like that. The robot rejects it; all it wants to see is "ROVER".
Obviously not difficult to fix manually! (I wonder if it wouldn't have
written those extra words if I hadn't hit "Enter" on them while writing
the file?)
> One idea I have had is to use the Cabrillo standard for the .DAT file. This
> would simply mean that everything needed for the QSO: entries would be in
> the log - and you can switch sent information on the fly. However, it also
> means that things like QSO points aren't there, and that would cause other
> issues. I doubt people are prepared to lose the score calculation during
> the contest.
I'm certainly not. I suppose you could store QSO points etc. in a
separate file but that kinda goes against the point of switching to
Cabrillo.
It's been quite awhile since I've read the Cabrillo definition. Are
there no provisions for comments within a QSO: line?
--
Doug Smith W9WI
Pleasant View (Nashville), TN EM66
http://www.w9wi.com
|