On 11/11/2015 21:42, Bill Somerville wrote: > On 11/11/2015 21:30, Joe Taylor wrote: > > Hi Joe, >> Thanks, Bill. Could be there never had been any code in WSJT-X to >> properly generate messages with compound callsigns -- either TYpe 1 or >> 2. I may have left that task as a "TBD" item. If need be, I can move >> the needed code over from MAP65, adapted as necessary for WSJT-X. > Now I am confused, it seems to be working for me in v1.5.0 and development. > > What is not working? Ah OK, I see the discrepancy against the User Guide where the generated reply to a CQ call is not a type 1 compound call message. IIRC this was done because a change was made such that a type 1 compound call user would have a standard message with their base call sign flagged as for them i.e. red background to the decode. Therefore the grid need not be dropped since a standard message suffices. The final 73 from the replying station uses the full compound call sign to indicate that the correct call is being logged. Another change at the same time ensured that the correct call is logged by the replying station. >> -- Joe > 73 > Bill > G4WJS. >> On 11/11/2015 4:20 PM, Bill Somerville wrote: >>> On 11/11/2015 20:55, Joe Taylor wrote: >>>> Bill, I think the code now used in genStdMsgs is yours. For some reason >>>> did you intentionally de-activate the way Type 1 callsigns were >>>> previously supported? Or am I forgetting the reason something was done >>>> here? >>> Not intentionally Joe, I thought the only changes were to accommodate >>> different ways of working with type 2 compound calls. >>> >>> Looking into it now. >>> >>> 73 >>> Bill >>> G4WJS.
------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
