[WT-support] Spaces preceding # Lua calls

[Clive Whelan]

Larry

More....yawn

You may already know this but just in case.

While eliminating any spaces before the trailing #TOGGLE RADIO Lua 
script call works just fine, as described below, doing the same ( I mean 
after the call ) for the first script call at the beginning of the 
message does NOT. What happens is that the script is completely ignored, 
the message is sent and then the trailing script IS executed, putting 
the system 180 degrees out of sync. This is not an issue as long as the 
user is aware of what is happening. This is why I originally put spaces 
between both calls as it just didn't look syntactically correct, even to 
a non programmer. Could confuse a stupid person ;-)

73


Clive
GW3NJW

Clive Whelan wrote:
> Larry
>
> Just f.y.i.
>
> The problem is definitely caused by a space in the text before the Lua # 
> call, and is equivalent to about 100 or 150mS per space at 32 w.p.m. The 
> execution of the Lua script call therefore is essentially instantaneous.
>
> Having eliminated the single space that I had inserted in the message 
> now means that my PTT tail is 50mS which is what is set in the PTT tab 
> of the router software for the MK2R+. This is fast enough not to chop 
> anything from the first dot of even fast QSK callers and yet sufficient 
> not to allow the PTT to drop out between message ( or paddle sent) 
> characters at slower speeds. I have used QSK for over 30 yeras now, but 
> in SO2R it's largely irrelevant as one is invariably listening on the 
> other radio when the primary radio is transmitting. Encore, tu peut 
> choisir ton gout!
>
> 73
>
>
> Clive
> GW3NJW
>
> Clive Whelan wrote:
>   
>> Hi Larry
>>
>> You are right that I have a space immediately before the  #TOGGLERADIO , 
>> not for readability but because I thought it would be syntactically correct!
>>
>> I will try without the space tomorrow ( aargh I mean today now!)
>>
>> 73
>>
>> Clive
>> GW3NJW
>>
>>
>> Laurent HAAS - F6FVY wrote:
>>   
>>     
>>> Hi Clive
>>>
>>> Clive Whelan a écrit :
>>>
>>>   
>>>     
>>>       
>>>> Using the wtApp:ToggleCapsLock()   chunk seems to be a little slow in 
>>>> execution ( maybe 100mS?), and at the end of a message delays the return 
>>>> to rx, so that fast calls have a dot or so chopped from them. Later 
>>>> today I will try the set and reset functions as an alternative. Perhaps 
>>>> this makes some sense to you but it puzzles me.
>>>>     
>>>>       
>>>>         
>>> I'd rather think the longest delay is caused by the extra space at the 
>>> end of your message, and not by the execution of the script.
>>>
>>> If your msg is
>>>
>>> BLAH #TOGGLERADIO
>>>
>>> the space will be taken into account by the parser of the keyer.
>>>
>>> If you use
>>>
>>> BLAH#TOGGLERADIO
>>>
>>> it will not. But it is much less readable. Chose your poison.
>>>
>>> 73
>>>
>>> Larry - F6FVY
>>> _______________________________________________
>>> 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
>>
>>   
>>     
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>