<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16809" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=140365619-20022009><FONT face=Arial
color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=140365619-20022009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=140365619-20022009><FONT face=Arial
color=#0000ff size=2>Ed - W0YK</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> support-bounces@win-test.com
[mailto:support-bounces@win-test.com] <B>On Behalf Of </B>Ron
Castro<BR><B>Sent:</B> Friday, 20 February, 2009 11:18<BR><B>To:</B>
support@win-test.com<BR><B>Subject:</B> Re: [WT-support] RTTY "and
NOW"<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial size=2>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!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> Ron
N6IE<BR> <A
href="http://www.N6IE.com">www.N6IE.com</A><BR></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=n6tv@arrl.net href="mailto:n6tv@arrl.net">Bob Wilson, N6TV</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=support@win-test.com
href="mailto:support@win-test.com">support@win-test.com</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, February 20, 2009 10:56
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [WT-support] RTTY "and
NOW"</DIV>
<DIV><BR></DIV>2009/2/20 Ron Castro <SPAN dir=ltr><<A
href="mailto:ronc@sonic.net">ronc@sonic.net</A>></SPAN><BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV bgcolor="#ffffff">
<DIV><FONT face=Arial size=2>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"</FONT></DIV></DIV></BLOCKQUOTE><BR>Right-clicking
is reserved for bringing up the "context menu" (pop-menu) for most windows,
so is therefore unavailable. <BR><BR>
<DIV class=gmail_quote>On Fri, Feb 20, 2009 at 10:15 AM, Iain MacDonnell -
N6ML <SPAN dir=ltr><<A
href="mailto:ar@dseven.org">ar@dseven.org</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><BR> $PREVCALL
TU NW $LOGGEDCALL $GUESSEXCH $F2<BR><BR></BLOCKQUOTE></DIV><BR>Perhaps the
Intelligent Quick QSL feature of Win-Test is the right place to add this
feature.<BR>
<OL>
<LI>In the MSGS window, [+] key: $QQSLC $CR<BR>
<LI>In the Quick QSL Window
<OL>
<LI>RTTY short QSL: $LOGGEDCALL TU NOW $INSERT
<LI>RTTY long QSL: $LOGGEDCALL TU DE $MYCALL
$MYCALL</LI></OL></LI></OL>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".<BR><BR>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.<BR><BR>To preserve the current function, maybe there
needs to be three quick QSL messages instead of only two:<BR>
<OL>
<LI>Short QSL: $LOGGEDCALL TU
<LI>Stacked QSL: $LOGGEDCALL TU NOW $INSERT (or $LOGGEDCALL
$CR TU NOW $INSERT ? )<BR>
<LI>Long QSL: $LOGGEDCALL TU DE $MYCALL $MYCALL
QRZ<BR></LI></OL>73,<BR>Bob, N6TV<BR>
<P>
<HR>
<P></P>_______________________________________________<BR>Support mailing
list<BR>Support@win-test.com<BR>http://www.f5mzn.org/cgi-bin/mailman/listinfo/support<BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>