I think we're talking at cross-purposes Bill - the "issue" described in 
the second paragraph (that of the default auto-generated messages being 
different for JT65 in WSJT-X vs WSJT) has nothing to do with the first 
paragraph, and nothing to do with short codes? I'm confused now :)

Regards, Mark


On 07/05/2016 15:03, Bill Somerville wrote:
> Hi Mark,
>
> comments in line below.
>
> On 07/05/2016 14:58, Mark Turner (EI3KD) wrote:
>> lots snipped, but the clip below what was I was looking for; so my
>> understanding is that it will be possible to auto-generate the "RO",
>> "RRR", "73" short-code messages instead of reports+signal strengths,
>> etc, for Tx3/4/5 in WSJT-X for EME, if we choose?
> Yes.
>> I do understand about the prefixes, although this isn't how WSJT (any
>> version) works for JT65 right now with the European default message
>> templates. As it stands, WSJT generates (for example) a Tx2 of
>> "EA6/PA2CHR EI3KD OOO", and WSJT-X generates "PA2CHR EI3KD -21" (or
>> whatever the report is), with "EA6/PA2CHR" entered in the DX Call textbox.
> The short code messages do not actually contain the callsigns, what is
> printed at both ends is inferred from previous parts of the exchange.
>
> 73
> Bill
> G4WJS.
>

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to