[WT-support] sending command to go to end of log? Re: problem with serial number while changing bands

[Bob Wilson, N6TV]

Here's a script named GoToEndOfLog.wts.  Save in your /scripts directory
and call from another script using wtScript:Call("GoToEndOfLog"), or assign
to a key.

Key lines:

-- Windows virtual key code constant
VK_END = 291      -- The End key (VK_END=0x23, 35+256 = 291)

-- Simulate Ctrl+End (Go to end of log)
wtApp:SendKeyCode(VK_END, WT_KEY_CTRL)

return -1

But I think you should change bands by typing the band name into the empty
logging window and pressing Enter, rather than using Alt+F1 or Alt-F2.  The
list of acceptable values in is in the Check Multipliers window (F10).

First, set Tools | Data Entry | Priority to *Band*

Next in the logging window, just type the band name to change bands:

50 [Enter] changes to 6m
144 [Enter] changes to 2m
19G [Enter] changes to 19 GHz band

73,
Bob, N6TV

On Sat, Feb 9, 2019 at 11:47 AM Alexander Kurpiers <a.kurpiers at gmail.com>
wrote:

> Hello,
>
> I was thinking about a good way to fix my issue (I still think allowing
> that changing the band of an already logged QSO is far too dangerous):
> before sending a command to change bands I would have to make sure that
> the log is at the end. Easy by keyboard (ctrl-end), but it seems it is
> not possible to send a remote command as there is no matching text command?
>
> 73' Alexander DL8AAU
>
> Am 24.11.2018 um 19:53 schrieb Alexander Kurpiers:
> > Hello,
> >
> > any chance to disable changing bands for logged QSOs?
> >
> > 73' Alexander
> >
> > Am 15.10.2018 um 10:32 schrieb Alexander Kurpiers:
> >> Hello,
> >>
> >> I was facing a weird problem: our operators managed to "reset" the
> >> serial number on one band...
> >>
> >>
> >> Trying to reproduce I found what went wrong:
> >>
> >> - log a QSO on one band
> >>
> >> - go up in the log to this QSO and change the band using band up/down
> >> arrows. The frequency changes, but rest stays as is (including the
> >> serial number)
> >>
> >> - the next serial you use on the band you changed this QSO to is wrong
> >> (and all QSOs after that one).
> >>
> >>
> >> Example: you log a QSO with number 010 on 5,7GHz. Now you change the
> >> band to 2,3GHz (where your number would be 028) - but the number stays
> >> at 010.
> >>
> >>
> >> Win-Test version 4.24.0, "European V/UHF - no multipliers".
> >>
> >>
> >> I would propose that you are not able to change the band of a QSO when
> >> you go up to in the log. Far too dangerous.
> >>
> >>
> >> (I just checked, still the case with 4.27.0).
> >>
> >>
> >> 73' Alexander DL8AAU
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20190209/d93b7b06/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GoToEndOfLog.wts
Type: application/octet-stream
Size: 564 bytes
Desc: not available
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20190209/d93b7b06/attachment.obj>