Re: [wsjt-devel] Sh messages not now working correctly in JT4 and QRA64

2017-07-17 Thread Bill Somerville
On 17/07/2017 16:33, Black Michael via wsjt-devel wrote: Fix sh msgs on QRA64 and JT4 https://www.dropbox.com/s/2sf3auzapz54m16/shmsg.patch?dl=1 de Mike W9MDB Thanks Mike, applied and merged to the v1.8 branch. 73 Bill G4WJS.

Re: [wsjt-devel] Sh messages not now working correctly in JT4 and QRA64

2017-07-17 Thread Black Michael via wsjt-devel
Fix sh msgs on QRA64 and JT4 https://www.dropbox.com/s/2sf3auzapz54m16/shmsg.patch?dl=1 de Mike W9MDB-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/sl

Re: [wsjt-devel] Sh messages not now working correctly in JT4 and QRA64

2017-07-16 Thread Bill Somerville
On 16/07/2017 18:51, char...@sucklingfamily.free-online.co.uk wrote: The other issue is that TX5 is now stuck on @1750 now whether Sh is ticked or not, and independent of type of mycall. It should toggle between @1750 and the [call call 73] message. This behaved correctly in rc1. Hi Charlie,

Re: [wsjt-devel] Sh messages not now working correctly in JT4 and QRA64

2017-07-16 Thread charlie
Hi All Further to last, part of the problem seems to be related to the use of a compound call as mycall. With mycall as G3WDG, TX6 toggles correctly with Sh between @1000 and [CQ G3WDG grid]. With mycall as HA/G3WDG TX6 stays stuck on CQ HA/G3WDG. I must admit I did not test the patch with compo

[wsjt-devel] Sh messages not now working correctly in JT4 and QRA64

2017-07-16 Thread charlie
Hi All Something has changed in RC1 and further changes in RC2 regarding behaviour of Sh messages in JT4 and QRA64, so that they no longer work correctly. If the program is opened having been closed with Sh ticked, the correct frequencies are in TX4, 5 and 6. Unticking Sh and ticking it again doe