On 03/03/2015 00:53, Joe Taylor wrote: > Bill -- Hi Joe, > >> The message is indeed a valid standard message but that is not the >> issue. The issue is that current software will not extract the report >> from a message that doesn't contain the DE call. > Maybe we're arguing semantics. When you say "the report will not be > collected at the far end" and "current software will not extract the > report", I assumed you were referring to the decoding process. I guess > you're worrying instead about automatically collecting the report sent > by someone else, so as to log that report correctly? That's right. > >>> The only possible downside of using these messages with a "Type 2" >>> prefix/suffix is that other "JT-compatible" programs (JT65-HF, etc.) may >>> not decode the messages correctly. >> And WSJT-X :( > I don't see that WSJT-X is similar here, at all. The other programs may > decode our Type 2 messages incorrectly. WSJT-X does not. Agreed but the received report is only captured (automatically) if the message contains the DE call sign i.e. if I decode:
DE TI4/N0URE R-10 WSJT-X does not record that -10 report unless I manually enter it. My rejection of my first proposal was based on the high probability that stations worked by type 2 compound call sign holder will not log their report correctly. We could change WSJT-X to collect any report from a double clicked message or slightly smarter any report from a message that has either the DE or DX base or full call in it, but as things stand every copy of WSJT-X in the field does not do that. Maybe such a change and a future change in the generated messages once we are comfortable that the change has high penetration in the user base. > > -- Joe 73 Bill G4WJS. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
