[WT-support] RTTY "and NOW"

[Ed Muns]

99% of the stations I worked last weekend were done so by "automatic
grabbing" of the call sign, so the proposed UI below should work great.  I
glance as the highlight(ed) call signs before hitting the key, and there
were very few I had to avoid.
 
Ed - W0YK


  _____  

From: support-bounces at win-test.com [mailto:support-bounces at win-test.com] On
Behalf Of Ron Castro
Sent: Friday, 20 February, 2009 11:18
To: support at win-test.com
Subject: Re: [WT-support] RTTY "and NOW"


Automatic grabbing of a call like that sounds dangerous since lots of junk
characters can look like call signs and wind up as the 'next' station.  I
can just visualize "N6TV TU TNX...NOW P5ABC 599 050" ...like I'm really
gonna work a P5 in an RTTY contest!
 
         Ron  N6IE
      www.N6IE.com


----- Original Message ----- 
From: Bob Wilson, N6TV <mailto:n6tv at arrl.net>  
To: support at win-test.com 
Sent: Friday, February 20, 2009 10:56 AM
Subject: Re: [WT-support] RTTY "and NOW"

2009/2/20 Ron Castro <ronc at sonic.net>


How about left-click on the first station, then right-click on the 'next'
station.  Instead of the normal F-key you use for "TU QRZ...", you use
Alt-and the same F-key to trigger "TU...NOW PY4XLZ 599 315"


Right-clicking is reserved for bringing up the "context menu" (pop-menu) for
most windows, so is therefore unavailable. 


On Fri, Feb 20, 2009 at 10:15 AM, Iain MacDonnell - N6ML <ar at dseven.org>
wrote:



 $PREVCALL TU NW $LOGGEDCALL $GUESSEXCH $F2




Perhaps the Intelligent Quick QSL feature of Win-Test is the right place to
add this feature.


1.	In the MSGS window, [+] key:  $QQSLC $CR


2.	In the Quick QSL Window 


1.	RTTY short QSL:  $LOGGEDCALL TU NOW $INSERT 

2.	RTTY long QSL:  $LOGGEDCALL TU DE $MYCALL $MYCALL

Since $INSERT is supposed to simulate pressing the [Insert] key, it should
grab the next call in the window (it probably doesn't work right today, but
maybe this can be fixed).  I have not tried it yet.  Maybe you'll need to
put the "$CR" after "$LOGGEDCALL".

Finally, Win-Test needs to always send the "short QSL" message whenever a
second unworked callsign is "stacked", regardless of the QSO count or timer.

To preserve the current function, maybe there needs to be three quick QSL
messages instead of only two:


1.	Short QSL:  $LOGGEDCALL TU 

2.	Stacked QSL:  $LOGGEDCALL TU NOW $INSERT  (or $LOGGEDCALL $CR TU NOW
$INSERT ? )


3.	Long QSL:  $LOGGEDCALL TU DE $MYCALL $MYCALL QRZ


73,
Bob, N6TV




  _____  




_______________________________________________
Support mailing list
Support at win-test.com
http://www.f5mzn.org/cgi-bin/mailman/listinfo/support


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20090220/638a17b0/attachment.htm