Hi Paul,
Thanks for calling my attention to the fact that the second message
under "Calling CQ" on Tab 2 is not generated correctly. It will be
fixed in the next release.
On Tab 1 I am presently inclined to leave things as they are. The idea
is that when you double-click on, say, "CQ DL1SBY JN49" the
automatically generated messages on Tab 1 give you the choice of
responding with Tx1 ("DL1SBY WA8UGN PK08") or Tx2 ("DE DU2/WA8UGN
PK08"). Tx1 is usually preferred, and therefore the default. It makes
it perfectly clear who you are calling, but it does not identify your
special status in DU2 and probably does not contain your legally
assigned callsign. Tx2 satisfies these concerns, but DL1SBY might not
realize you are calling him.
If you are using Tab 1 and calling CQ, double-clicking on a responding
callsign will automatically generate something like
"DL1SBY WA8UGN R-15" for Tx3. You can use this to respond; or better
still, use Tx3 but manually change "R-15" to "-15".
We could, of course, generate "DL1SBY WA8UGN -15" for Tx2... it's a
judgment call whether that would be more useful than generating
"DE DU2/WA8UGN PK08".
I am taking the liberty of copying this response to the "wsjt-devel"
mailing list, so that others in our development group will know what we
have discussed.
-- 73, Joe, K1JT
On 10/7/2014 10:51 AM, Paul Keating wrote:
> Am testing “wstjx-1.4.0-rc2” (Beta Version 1.4) and noted a problem when
> generating standard messages:
>
> For either Tab 1 Message “Tx 2” or Tab 2 Message “dB” the beta program does
> not generate the proper message of “Call1 Call2 dB” but generates the
> message of “DE Call2 Locn” in its place.
>
> Problem appears to be peculiar to “My Call” using a portable designator and
> 10 characters in length.
>
> Examples of all messages generated, using “My Call” of DU2/WA8UGN:
>
> Tab 1 Tab 2
>
> DL1SBY WA8UGN PK08 Tx 1 CQ: CQ DU2/WA8UGN PK0
> DE DU2/WA8UGN PK08 Tx 2 Grid: DL1SBY WA8UGN PK08
> DL1SBY WA8UGN R-15 Tx 3 Db: DE DU2/WA8UGN PK08 ß
> DL1SBY WA8UGN RRR Tx 4 R+Db: DL1SBY WA8UGN R-15
> DE DU2/WA8UGN 73 Tx 5 RRR: DL1SBY WA8UGN RRR
> CQ DU2/WA8UGN PK08 Tx 6 73: DE DU2/WA8UGN 73
>
> In “WSJT-X v1.3, r3673,” a similar problem exists, but only on Tab 2 Message
> “Grid” (so work-around via Tab 1 is possible):
>
> Tab 1 Tab 2
> DE DU2/WA8UGN PK08 Tx 1 CQ: CQ DU2/WA8UGN PK08
> DL1SBY WA8UGN -10 Tx 2 Grid: DE DU2/WA8UGN PK08 ß
> DL1SBY WA8UGN R-15 Tx 3 Db: DL1SBY WA8UGN -10
> DL1SBY WA8UGN RRR Tx 4 R+Db: DL1SBY WA8UGN R-15
> DE DU2/WA8UGN 73 Tx 5 RRR: DL1SBY WA8UGN RRR
> CQ DU2/WA8UGN PK08 Tx 6 73: DE DU2/WA8UGN 73
>
> Platform: SONY VAIO model VPCCB25FX
> O/S: Windows 7
> Interface: SignaLink USB
> Ancillary Program: JTAlert-X 2.4.20
>
> Best regards& 73,
>
> Paul A. Keating
> DU2/WA8UGN
> Pasuquin, Ilocos Norte, Philippines
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
