Perhaps a special keystroke to duplicate the previous QSO without changing
the serial number? Such that one enters the QSO with the first mult as
usual. Then the special keystroke duplicates all previous information
except for the multiplier. Once the second mult is entered, ENTER puts
the QSO in the log without sending any acknowledgement.
I obviously have no idea about how the internals of either LOG or POST
would deal with such buggery of the serial number or auto-send features...
This might be a problem in multi-op situations where other QSOs on the
network appear in the buffer at inopportune times. One would have to have
the last QSO stored in a separate buffer.
My programmer tendencies are showing...
73, 0-bat
>
> > Did we ever come up with a good way of handling county line contacts for
> > QSO
> > parties? I know how to deal with rovers using a /M1, /M2, etc on the end of
> > the call. The problem is the multiple mults, zero Q point contact county
> > line
> > stradlers. If I just dupe a new county the serial number gets hosed. Do we
> > need a 'NO QSO INCREMENT ON DUPE' logcfg.dat item(!!!! yikes not another
> > !!!!)
> > or did I miss the fix?
>
> This is a messy thing - the only way I know to do it is to log
> the two QTHs with a / between them. Put the one you need as a
> mult first.
>
> Tree
>
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|