[WT-support] New Lua APIs

[Laurent HAAS - F6FVY]

Hi

Bob Wilson, N6TV a écrit :

> First, why do all the wtRadio* functions end with an asterisk at the 
> end, and the other functions do not?

It is described in the APIs list :

> CAUTION : The following functions can apply to:
> wtRadio (the active one),
> wtRadioInactive (the non-active one),
> wtRadioPrimary (the one that is in the main log wnd)
> wtRadioSecondary (the one that is in the secondary log wnd)
> wtRadio1 and wtRadio2

It means that wtRadio*:Blah() is the generic description of the 
following functions :

wtRadio:Blah()
wtRadioInactive:Blah()
wtRadioPrimary:Blah()
wtRadioSecondary:Blah()
wtRadio1:Blah()
wtRadio2:Blah()

> But I could write a ClearRIT functoin that works with /all/ my radios, 
> not just the K3, if there was a "GetRadioType" function and a list of 
> radio type constants.

Noted.

> So, can you give us a way to call any LUA function from a CW or RTTY 
> message?

It is described in the release.txt file :

> - Scripts can now be called from a CW or a RTTY message. You must use
>   the #SCRIPTNAME(ARGUMENT) notation. The argument (and parenthesis)
>   are optional. The script will be called synchroneously, but is
>   executed in the main thread, meaning that it is not blocking the
>   CW/RTTY stream.

For example :

TU N6TV #CLEARRIT  (assuming your script is called CLEARRIT.wts).

or

TU #QSYUP(200)  (assuming you created a script named QSYUP.wts to QSY up 
wtArgument Hz after a QSO)

> Finally, are there plans to add more wtContest functions so that we can 
> eventually write a complete LUA script to support a "User Defined 
> Contest" type for usupported contests?

Not yet.

73

Larry - F6FVY