[WT-support] Using the partner window as a scratchpad when you hear multiple callsigns in a pileup
Bob Wilson, N6TV
n6tv at arrl.net
Wed Sep 29 09:42:44 CEST 2010
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
>
>
>
> Il giorno 29/set/2010, alle ore 05.27, Bob Wilson, N6TV ha scritto:
>
> Let's say you're a big gun DX station, and you can pick out three or four
> callsigns in a pileup, but you just can't remember them all.
>
> I've created a little Win-Test LUA script called "StackCalls" to attempt to
> solve the "scratchpad" problem.
>
> The script below lets you enter as many calls at once as you like and
> stacks them in the partner window. By default, calls are stacked in reverse
> order (last one at the top), then the last call enetered is loaded into the
> logging window, ready for you to call back. The rest of the callsigns heard
> remain "stacked" in the partner window, and may be grabbed via Alt-1, Alt-2,
> or double click. To simply remove a callsign from the Partner window, you
> can use Ctrl-Double click.
>
> You also have the option of stacking callsigns in the order entered (First
> in First Out), rather than in reverse order (Last in First Out).
>
> How to install:
>
> 1. Save StackCalls.wts (below) in your Scripts directory (to see this
> directory, in Win-Test, do File | Explore | /scripts directory)
> 2. Tools | Scripts Manager
> 3. Highlight StackCalls and click the [Properties] button
> 4. Click the [Define] button
> 5. Press [F12] or [Ctrl-C] or whatever key you wish to use to activate
> StackCalls
> 6. If you want callsigns to be stacked in the order entered, enter
> Argument: "FIFO" (*with* the quotes),
> otherwise enter no argument
> 7. Press [OK]
> 8. Press [OK] again
>
> How to use:
>
> 1. Windows | Partner (once, to keep the Partner window visible; my
> attempt at automating this did not work)
> 2. Press [F12] or whatever key you assigned to StackCalls
> 3. In the pop-up window, type as many callsigns as you like and press
> Enter
> 4. Note that all the callsigns are now loaded in the partner window,
> one per line, except for the last one entered, which should be in the
> logging window (unless there was already a callsign in the logging window)
> 5. Use Alt-1 to pick off the next most recent call, or any other you
> wish
> 6. Press Alt-1 multiple times to pop every callsign off the stack.
>
> I hope this helps.
>
> For more details of how to use the Partner Window, see this page<http://docs.win-test.com/wiki/Menu:Windows#Partner>in the Win-Test Wiki.
>
> 73,
> Bob, N6TV
> *
> StackCalls.wts*:
>
> -- Stack Calls - Stack multiple callsigns in partner window so that they
> can be
> -- grabbed one at a time with Alt-1, Alt-2, etc.
> --
> -- Assign to: F12, Ctrl-C, etc.
> --
> -- Argument = none for LIFO (last in, first out) - default
> -- "FIFO" (in quotes) for first in, last out
> -- Time-stamp: "29 September 2010 03:23 UTC"
> -- Written by N6TV
>
> local lifo = true -- Assume last in, first
>
> if wtArg ~= nil and string.upper(wtArg) == "FIFO" then
> lifo = false
> end
>
> -- Prompt for callsigns
> local callsigns = wtApp:InputText("Enter callsigns:", wtCurrentScript, "")
>
> local callsign = nil
> -- If user didn't simply press Escape or Cancel or enter nothing
> if callsigns ~= nil and callsigns ~= "" then
> -- Make Partner Window visible
> -- wtApp:ShowWindow(WT_WND_PARTNER)
>
> if lifo then
> -- We want last in, first out, so first we have to reverse the string
> of callsigns
> callsigns = string.reverse(callsigns)
> end
>
> -- If there's already a callsign in the logging window, save it in the
> stack
> if wtQso:IsCallsignEmpty() == false then
> -- Type Alt-Enter to save it the partner window
> wtApp:SendKeyCode(269, WT_KEY_ALT)
> end
>
> -- For each callsign entered in the box (alphnumeric characters (%w) and
> slashes)
> for callsign in string.gmatch(callsigns, "[%w/]+") do
> -- Clear the callsign field in the logging window
> wtApp:SendFKey("F11")
>
> if lifo then
> -- Unreverse the callsign
> callsign = string.reverse(callsign)
> end
>
> -- Type the callsign in the logging window
> wtApp:SendKey(callsign)
>
> -- Type Alt-Enter to load it into the partner window
> wtApp:SendKeyCode(269, WT_KEY_ALT)
> end
>
> -- Finally, type Alt-1 to pop the last callsign heard, or to restore
> call that was already
> -- in the logging window if nothing was entered in the pop-up window.
> wtApp:SendKey("1", WT_KEY_ALT)
> end
>
> -- No further keystroke processing
> return -1
>
> <StackCalls.wts>_______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>
>
> _______________________________________________
> 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/cd2cf0a4/attachment.htm
More information about the Support
mailing list