[WT-support] $OPNAME - small bug

Bob Wilson, N6TV n6tv at arrl.net
Sat Feb 16 10:06:15 CET 2019


Did you right click on the Extra Data Window and set Actualize Information
to "Automatically"?  You should not have to send $LOGGEDCALL to make it
work.

73,
Bob, N6TV

On Sat, Feb 16, 2019, 1:00 AM John Warburton G4IRN <qrz at dxdx.co.uk> wrote:

> Hi Bob
>
> Thanks for getting back. Rather confused by your response I set out to
> recreate this again - I believe I have found the reason for what I found.
>
> I think the $OPNAME macro has to be preceded by the associated $LOGGEDCALL
> macro - WT uses the logged call-sign as the look-up value in the .xdt file.
>
> The 'error' use -case is this:
>
> Assuming names file below is loaded in the Extras directory, selected in
> Options|Data Files. I'm using a DXpedition file for simplicity.
>
>    - In run mode type G0BNR in the logging line
>    - press insert (Insert= $LOGGEDCALL $F2; F2= $OPNAME 5NN)
>    - CW sent is as expected ('G0BNR Nigel 5NN')
>    - Press Plus to log the QSO (Plus = TU $CR)
>
>
>    - Switch to S&P mode
>    - Type G0AJC (you've just tuned into his CQ)
>    - Press F4 (F4=$MYCALL) to call him
>    - When he comes back and gives his report, I press $F2 to send his
>    name and report
>    - CW sends 'G0AJC Nigel 5NN' - i.e. the name of the last $LOGGEDCALL
>    sent, not the guy I am working.
>
> So this is working 'as designed' but sends an incorrect name in the
> context - I believe this is because $LOGGEDCALL does not get sent in this
> S&P scenario; the work-around is to add $LOGGEDCALL to the S&P message.
>
> Thanks
>
> John G4IRN.
>
>
> On 15/02/2019 18:18, Bob Wilson, N6TV wrote:
>
> I can't replicate this problem.
>
> Of course you have to type a callsign into the logging window after
> switching to S&P mode, then press F2.  Perhaps you are typing the callsign,
> then switching to S&P mode?
>
> 73,
> Bob, N6TV
>
> On Fri, Feb 15, 2019 at 9:50 AM John Warburton <qrz at dxdx.co.uk> wrote:
>
>> Hi
>>
>> A friend has passed this to me, I've tested it and find the same bug as
>> him. I hope I'm not doing anything stupid!
>>
>> Create an .xdt file to define names with the $OPNAME variable e.g.
>>
>> # VARIABLE $OPNAME
>> G0AJC Giles
>> G0AJJ Linda
>> G0BBB Uri
>> G0BBV Hedley
>> G0BJK DAVE
>> G0BNR Nigel
>>
>> Put $OPNAME in a RUN message and an S&P message e.g.
>>
>> Run/F2 = $OPNAME 5NN
>>
>> S&P/F2 = $OPNAME 5NN
>>
>> In RUN mode the name sends OK, switch to S&P and the last name sent in
>> RUN mode gets sent again, irrespective of the call-sign logged.
>>
>> Thanks
>>
>> John G4IRN
>>
>>
>>
>>
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20190216/6f5a1996/attachment-0001.html>


More information about the Support mailing list