I have had several qso's this evening using 5056 both calling cq and answering cq calls and the double clicking the sent text for a reply worked fine as did the log input but all calls were standard calls.
The 1 thing I noticed was I started to call cq but got distracted a station replied and I never noticed, while tx was still enabled it did not send a 2nd cq it waited for me to reply so it missed a minute, normally it would continue to call cq, I noticed after the station called me twice and the qso went ahead as normal. Richard m0clz -----Original Message----- From: Bill Somerville Sent: Saturday, March 14, 2015 7:26 PM To: WSJT software development Subject: [wsjt-devel] WSJT-X: automatic processing of received messagesenhancements Hi All, I have just committed the second phase of my changes related to compound callsigns to the development branch. Here is the commit message: ------------------------------------------------------------------------ r5055 | bsomervi | 2015-03-14 19:13:18 +0000 (Sat, 14 Mar 2015) | 21 lines Improved automatic message handling More consistent and accurate processing of compund callsigns including recognizing the user's call in both base and fully qualified form, extracting reports from special type one and type two compound call messages. Ensure that "CQ DX" message prefixes are recognized and processd correctly. The cycle of double clicking through a QSO has been enhanced to recognoize the standard messages correctly and use the correct next message. The automatic transmission button "Enable Tx" now does what it says and does not double as a stop transmit button. This allows the current transmission to complete even if the automatic transmission feature is disabled. In line with this the "stop sending after a 73 message is sent" feature turns off the automatic transmission enable at the start of the sending of a 73 message and also the next message is now set up as the CQ message automatically in this scenario. A 73 message is now either a standard message containing the word "73" or any free text message containing "73" (not necessarily as a distinct word"). ------------------------------------------------------------------------ This change is a fairly radical reworking of the way incoming messages are parsed and the actions taken when messages are double clicked in the activity windows. It should handle QSOs by and with compound callsign holders far better than previously and has other benefits for all QSO types. I strongly recommend that testers experiment with using double clicks in the activity to progress their QSOs and report back any incorrect behaviour of the application. With these changes I find that having the settings "Double-click on call sets Tx enable" and "Disable Tx after sending 73" both checked makes the QSO process extremely smooth using just double-clicks on calls and responses, only having to revert to specific clicks and typing when I want to send a free text message or if my QSO partner sends an out of sequence message. If you are testing these changes; please double check that, when you come to log the QSO, the callsign, the report sent and received have been correctly transferred to the "Log QSO" pop up dialog. 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 ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5751 / Virus Database: 4306/9299 - Release Date: 03/14/15 ------------------------------------------------------------------------------ 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
