[WT-support] New features just added to dev. version

[Ed Muns]

This is great news.  I don't have time to test it right now, but one caution
is that the $PREVCALL must be the previous call ON THE SAME BAND, not simply
the last call in the log.  WriteLog currently has a bug where this message
parameter grabs the last call in the log.  If another band logs a QSO in the
middle of the "NOW" operation, then the TU $PREVCALL is from another
transmitter/band and doesn't make any sense.
 
Ed - W0YK


  _____  

From: support-bounces at win-test.com [mailto:support-bounces at win-test.com] On
Behalf Of Bob Wilson, N6TV
Sent: Wednesday, 04 March, 2009 20:18
To: Win-Test Reflector
Subject: [WT-support] New features just added to dev. version


Laurent just quietly added a bunch of new message variables to the
development version of Win-Test, including some that will make the "NOW"
message a possibility.

I encourage RTTY types to try it and make a constructive suggestions.
Multi-multi's using the partner window also might be able to use it.

http://download.win-test.com/nightly/wt_dev.zip

73,
Bob, N6TV

>From http://download.win-test.com/nightly/release.txt:

- RTTY windows : The middle-click acts the same as the left click in
  the stream display, except that selection is stacked in the Partner
  window.

- RTTY and CW : New variables.

  $CURRENT (or $CURRENTCALL) : Insert the callsign of the current QSO
  *despite* if a $CR (that it always executed on message keypress) is
  contained later in the message.

  $NEXT (or $NEXTCALL) : Send the callsign of the next QSO line when
  the $CR is included in the message.

  $PREV (or $PREVCALL) : Send the callsign of the previous QSO line.

  $GRABPARTNER : Grabs the first callsign from the Partner window and
  insert it in the callsign field.

  To summarize, you can now enter a QSO (with correction or not),
  grab another callsign from the Partner window and send his report
  in one keystroke, by using :

  $CORRECT TU $CR NOW $GRABPARTNER $NEXT $GUESSEXCH $F2 (w/correction)

  or

  $CURRENT TU $CR NOW $GRABPARTNER $NEXT $GUESSEXCH $F2 (full call)

  If you want to manually grab a callsign from the Partner window
  you can use :

  $PREV TU NOW $LOGGED $F2

  1/ Use enter to enter the current Q
  2/ Grab the next callsign from the Partner wnd (dbl-click or Alt-n)
  3/ Send the above message

- Custom variables support added. Mostly designed for the DXPed mode,
  this feature allows to create custom variables and set the value
  very quickly. Example : $REGION or $UP for a split up value.

  Use the Options / CW (or RTTY) / Custom variables... menu to set
  the names and the value of these variables to be used in your CW or
  RTTY messages. You can also use the VARIABLES text command.

  You can also easily set a variable value by entering its name in
  the callsign and "Enter". WARNING : Don't chose a variable name
  that is already used or it won't work...
  
  Tnx K5AC @ K5D. 




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.win-test.com/pipermail/support/attachments/20090304/d677cafd/attachment.htm>