[WT-support] multi ops runs

[Bob Wilson, N6TV]

On Dec 28, 2007 3:56 PM, <Georgek5kg at aol.com> wrote:

>   However, when I export the log (txt, csv, or adi), the operator callsign
> or nickname DOES NOT appear in the record.
>

Did you select "Operator" as one of the fields to export?  After typing
WRITELOG, Click [Options...] next to "Text file" and select "Operator" as
one of the Fields to export.  I just tried it and operator callsign appeared
in all exported files OK, including the ADIF file.

More info from Release.txt in
http://download.win-test.com/nightly/wt_dev.zip :

3.19.0-dev

* MZN

* FVY

- Basic Operators management

  Foreword : This feature is very limited, and will *not* be further
  extended in this major version of Win-Test (v3). It is mainly added
  to help DXPeditioners for the web log search scripts, and for
  various DX or contesters challenges (RRDXA etc.)

  New text commands : OPON (or LOGIN), OPOFF (or LOGOUT).

  This feature is only available to multi-op logs.

  If you entered a list of operators in the contest settings dialog
  when creating the log, it will be parsed to init the combo-box. You
  can add ops "on the fly" to this combo box.

  If you add nicknames to ops of this list (joe, jack, william,
  averell, josette or whatever - letters and numbers are accepted,
  allowing exotic nicks like l33t etc.), you can enter them as text
  commands to quickly change operator, without using the OPON command.

  Op. callsigns are limited to 7 chars, while nicks are limited
  to 13 chars.

  The operator changing is propagated across the network, meaning
  that if you login on a station, you will be automagically logged
  out of the previous one you were logged on (if any).

  The ADIF file export includes the op callsign in the QSO record, if
  an op. has been defined for that QSO.

  The text and CSV export files are also enhanced to allow the
  inclusion the op. callsign.

73,
Bob, N6TV
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20071228/86c2a5ce/attachment.htm