On 03/03/2015 01:11, Joe Taylor wrote: > Bill -- Hi Joe, > >> 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. > Yes. I wasn't too worried about that; we do, after all, offer a chance > to edit logging information before accepting it. See below. > >> 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. > This will provide a good incentive to upgrade. :-) Not really as the change benefits type 2 call holders but the upgrade has to be by everyone else. > > Obviously, logging a received report incorrectly is not what we want > users to do; but it seems to me not a very big deal if it sometimes > happens. For most purposes (DXCC, etc.) that does not invalidate a contact. Ok, but it is likely to impact nearly every QSO when a type 2 call replies to CQ calls. Given that type 2 calls are rare, other users will become habituated (probably already are) that double clicking a received report does the right thing and I doubt they will notice that it goes wrong were we to start having type 2 calls sending:
DE <type-2-call> R<report> small impact for most, big impact for type 2 call holders. Either way, I am making the required change so that WSJT-X will extract a received report from a standard message containing only the QSO partner call sign. This seems safe and proper to me. > > -- 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
