I think the idea is that they want the "@" to remain. But if it's always "@NNNN" with N=frequency could JTAlert allow that through without substitution?
RRR Mike W9MDB On Fri, Dec 18, 2015 at 2:49 PM, Laurie, VK3AMA <[email protected]> wrote: > On 19/12/2015 6:04 AM, Bill Somerville wrote: > > I believe the issue may lay with JTAlert which uses macro characters to > substitute names etc. in free text messages. If it is possible for > JTAlert to leave in an '@' character then this may be best addressed there. > > I will leave well alone. > > 73 > Bill > G4WJS. > > This is not a JTAlert issue. JTAlert never sends the "@" in the free-text > message. A Regex subtitutes the "@" character with the Callsign of your > QSO partner. In the unlikely event the Callsign is unknown, the "@" is > replaced > with an empty string. This can be observed by hovering the mouse over the > JTAlert macro button (that contains the "@" character) where the tooltip > displayed will show the resulting substituted text. > > "@" is NEVER sent to WSJT-X by JTAlert. > > de Laurie VK3AMA > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > >
------------------------------------------------------------------------------
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
