[WT-support] RTTY window change

[W1UE]

Rich

You didn't mention a Call History File.  If you have a decent Call 
History File working, the state/province is autofilled when you use the 
INS key to load the entry window.  You still need to check it (some of 
them are wrong, or some are operating out of their normal state), but 
its a great time saver.  Another benefit of a CHF, when you are tuning 
across a band and a call is copied where you haven't worked the state, 
the call will light up with the "unworked state" color.  Lets you know 
right away that you need the state.  Also, the zone is filled in 
depending on the state.  Very neat.

For the next routine, I programmed a key as follows:
{ENTER}! TU {LogThenGrab}NOW {F5} {F2}{ENTER}{Rx}
It sends TU to the guy I just worked, grabbed the next call from the 
Grab window, sends NOW and then the normal report sequence.  Worked OK, 
but, when a station sends "KL7RA 599 01 01 KL7RA", the last KL7RA goes 
to the top of the grab window and is the call that would be grabbed from 
the stack using my NEXT key.  For the RTTY Roundup, I think I'm going to 
look at converting myself to using the STACK routines instead of the 
GRAB routines to avoid that problem.

Nice to work you on 20M.  Wish we could have made it on more bands.

Dennis W1UE


On 9/27/2010 4:08 AM, KL7RA wrote:
> During the WW RTTY running Europe was easy using just the Ins and + keys
> but working USA requires you to use the mouse to load the zone and state.
>
> One nice change to the RTTY window is to move the Ins and + boxes from the
> right hand side to the left so they will be closer to the text allowing you a faster
> response to the caller. Also if the boxes were a color or different shape it might
> help your eye find them quicker.
>
> With CQ in auto mode the timer stops when you enter something into the logging
> window but for RTTY clicking a call into the logging window does not stop the
> CQ cycle and a CQ will start.
>
> On an tty operations note what is the best technique to load the next caller by
> using the msg "next" then the call. Most everything I tried this weekend didn't
> work as I hoped but I hear others are doing this smoothly.
>
> 73 Rich KL7RA
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>