Duh! Now why didn't *I* think of that. It works just like I want it to. I'd
have to say it's somewhat non-intuitive and definitely undocumented -- for
example, in CT or NA you just issue a command like "WORKDUPE" OR
"NOWORKDUPE" (not the greatest syntax, but more intuitive.) Perhaps the help
file section should illustrate how to configure for working dupes or not
working dupes? However, it does show how flexible Writelog's design is.
There's a real trade-off in this case between flexibility and ease of use.
Thanks for the help, Barry.
73, Dick WC1M
> -----Original Message-----
> From: Barry N1EU [mailto:n1eu@hotmail.com]
> Sent: Sunday, February 25, 2001 8:25 AM
> To: dick.green@valley.net; writelog@contesting.com
> Subject: Re: [WriteLog] More Suggestions
>
>
> Dick, you need to encode your messages to send the dupes. No
> problem with
> WriteLog. To send "599 NH", use this: %C %B5NN NH%B5NN NH
>
> 73,
> Barry N1EU
>
> P.S. Congrats on the great effort in ARRL CW!
>
>
>
> >From: "Dick Green" <dick.green@valley.net>
> >
> >More ideas for improvement:
> >
> >1. I try to work all dupes (better chance for lower UBNs.) Therefore, my
> >exchange function key contains "%C <exchange>" (no %B%B string.)
> When I hit
> >INSERT to work a dupe, Writelog stops after the callsign is sent and does
> >not send the exchange. This means I have to wake up, realize what's going
> >on, and reach over to hit the exchange function key manually.
> Since I work
> >75-100 dupes in a big contest, this is a real pain. Writelog sends the
> >exchange for a dupe only if I space or tab after entering the
> callsign and
> >before hitting INSERT. This is not desirable because I don't usually move
> >the cursor out of the callsign field until the other station responds. I
> >can't think of any reason why someone would want Writelog to
> work this way.
> >Also, this doesn't seem to be what the help file says will happen for the
> >Special Case: "Any characters following the %C in the memory are
> held until
> >you tab or space out of the CALL field, or until the message being sent
> >catches up to your typing, or if you stop typing for more than 1 second.
> >WriteLog doesn't do any of these things -- it just stops. Resuming after
> >one
> >second would probably be OK, but it doesn't do that (even if you
> continue
> >to
> >enter characters in the callsign and stop typing.)
> >
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|