HI Laurie,
comments in line below.
On 16/06/2016 01:00, Laurie VK3AMA wrote:
On 16/06/2016 8:33 AM, Bill Somerville wrote:
I thought the problem was WITHOUT doing such things there were some
CQ patterns that you could double-click in WSJT-X and it would
work...but double-clicking from JTAlert would not for some odd reason.
Maybe the fixes you did to the CQ QRZ and such fixed those edge cases?
That was the intention.
It is important to remember, JTAlert will always color CQ Callsigns
that will never be acceptable to WSJT-X. These particular decodes are
targeted destination style CQ,s with 2 letter abbreviations for US
states or Continents or free-form QRZ style messages
eg.
CQ EU VK3AMA
CQ NA VK3AMA
CA CA VK3AMA
It is also important to remember that JT65 and JT9 are designed to be
used with strictly formatted standard message forms. The addition of
free text messages is to enable a personalized "73" message to be sent
once a QSO is completed. WSJT-X does interpret some free text messages
as if they were closely related standard messages and some concessions
have been agreed for useful cases for example CQ9DX ... and CQ DX ...
(and now CQDX ...) being treated as equivalent to messages of the type
CQ ... or QRZ ... or DE ... but these are only possible due to
coordinated acceptance in all software and with the issue that old
versions cannot conform. The former concession makes it just about
possible to make a QSO with some short but not acceptable to WSJT-X
callsigns. For example, again contrived but nevertheless correct, it is
possible to have a QSO with a station having a callsign of A1 by double
clicking through the QSO sequence. The messages used will all be free
text messages but it will work. OTOH you will be in trouble if C123AAA
called as the generated messages would be truncated free text messages
with insufficient room to pass reports or rogers.
I have explained above that the CQ plus a two or three character
alphabetic word followed by a callsign and optional grid could also be
added as accepted forms by utilizing the spare E9AA-ZZ and E9AAA-ZZZ
callsign series, but this has not yet been agreed and coordinated. Until
that happens the above messages are free text messages and not treated
as general calls that can be replied to.
What I want to achieve is for the "Double-click" indicator of JTAlert
to only be visible to the end user when the UDP Reply Command ia
acceptable for that particular decode. So for the above examples
JTAlert will still alert a CQing station, but not indicate it is
double-clickable.
That's fine if you wish to do that, you should probably do the same for
any CQ AA-ZZ ... or CQ AAA-ZZZ ... message to be consistent.
The recent changes made to WSJT-X to improve CQ indicator accuracy do
nothing for JTAlert with respect to its "double-clickable" indicator
as these changes are invisible to JTAlert.
That is incorrect, you pointed out that QRZ ... messages were not
responsive to UDP reply requests, that should no longer be the case. Now
that they are, the last major inconsistency of WSJT-X responding to UDP
reply requests to valid general call messages should be rectified.
73
Bill
G4WJS.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
