[WT-support] Using the partner window as a scratchpad when you hear multiple callsigns in a pileup

[Fabio I4UFH]

Just amazing ! Now is clear how to use it !  Thanks again for this  
pièce of code !!

73 de i4ufh

Inviato da iPhone

Il giorno 29/set/2010, alle ore 15.36, Tõnno Vähk  
<Tonno.Vahk at gafm.ee> ha scritto:

> THIS IS FANTASTIC!!! Bob is a genius!
>
>
>
> I seem to really fall in love with this script thing. I hope one day  
> when I am retired I will be able to write some myself.
>
>
>
> I activated the StackCalls scripts and programmed another message:
>
>
>
> ++$CORRECT ++TU---- $CR $GRABPARTNER $NEXT $SPACEBAR $GUESSEXCH $F2
>
>
>
> And when I copy two calls from pileup I write first normally to  
> callsign window, have AUTOSEND send him exchange and then press F12,  
> write call and ENTER. Now I fill the exchange from the fist station  
> (unless it is automatically filled) and simply press the key with  
> the message above. It sends TU, corrects if necessary, grabs the  
> call from partner window, sends exchange, fills exchange..
>
>
>
> All with one keystroke. How cool is that??
>
>
>
> And advantage to ALT+ENTER is of course obvious – you can enter the  
> second call while you have first one on your callsign window. That i 
> s the whole point. ALT+ENTER is not usable at all.
>
>
>
> The only thing I noticed is that I am using $SPACEBAR and cursor  
> moves to exchange field after I press INSERT. Now F12, callsign and  
> ENTER activates another ENTER and cursor moves back to the callsign  
> field. That is wrong because I need it to stay on exchange field to  
> be able to enter exchange for the first station.
>
>
>
> Can you do so Bob, that ENTER to close StackCalls window is not  
> double-affecting the ordinary cursor position?
>
>
>
> tonno
>
>
>
> From: support-bounces at win-test.com [mailto:support-bounces at win- 
> test.com] On Behalf Of Bob Wilson, N6TV
> Sent: Wednesday, September 29, 2010 10:43 AM
> To: support at win-test.com
> Subject: Re: [WT-support] Using the partner window as a scratchpad  
> when you hear multiple callsigns in a pileup
>
>
>
> If you only copy one or two callsigns at a time and you find it easy  
> to press Alt-Enter, the script offers no advantage
>
>
>
> If you have a large unruly pileup, and decide to take your time and   
> pick out pieces of four or five callsigns or more then work them all  
> one after another without QRZ, you can simply enter them all at once  
> with far easier keystrokes.
>
>
>
> Try it with StackCalls assigned to F12:
>
>
>
> [F12] call1 call2 call3 call3 call4 [Enter]
>
> vs.
>
>
>
> Call1 [Alt-Enter] Call2 [Alt-Enter] Call3 [Alt-Enter] Call 4
>
>
>
> I think you'll find StackCalls a lot easier to use, though you can  
> still use both methods interchangeably.
>
>
>
> Note that you can also press [F12] to open up a second data entry  
> window for other calls you hear while you still have a callsign in  
> the logging window.  You cannot do that with Alt-Enter;  you would  
> have to press Ctrl-9 or something to save that callsign then restore  
> it with Ctrl-9 again, after pressing Alt-Enter.  That's a lot of work.
>
>
>
> 73,
>
> Bob, N6TV
>
>
>
> On Wed, Sep 29, 2010 at 12:03 AM, Fabio I4UFH <i4ufh at libero.it> wrote:
>
>
>
> Hi Bob,
>
>
>
> thank's for ur effort with this new LUA script !
>
>
>
> I want ask u which are the advantages of using this script, instead  
> of simply keep open the partner window and type calls in
>
> the callsign field  and pressing ALT RETURN to fill the partner  
> window, without logging the callsign.
>
>
>
> U solution it's one keystroke more longer that the "native" ALT  
> RETURN partner stack filling process.
>
>
>
> Let me know, i am loosing something
>
>
>
> 73 de Fabio I4UFH
>
>
>
> _______________________________________________
> 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/20100929/cb2c4f1d/attachment-0001.htm