How about suppressing the message though if m_dialFreq=18446744073709551615 ?? Would preclude any complaints in the future.
73 Mike W9MDB <https://www.avast.com/?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> This email has been sent from a virus-free computer protected by Avast. www.avast.com <https://www.avast.com/?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Nov 21, 2015 at 4:59 PM, Bill Somerville <g4...@classdesign.com> wrote: > On 21/11/2015 22:36, Michael Black wrote: > > WSJT-X: Dial frequency changed to 18446744073709551615 > > > > Is that a bug in the daemon or WSJT-X sending a bogus message? > Hi Mike, > > it is a complex Chicken and Egg scenario. The startup starts with > frequency zero and somewhere a small offset gets subtracted and the > Frequency wraps around. It sorts itself out very quickly when the first > update from the rig arrives. Personally I like it because if something > is wrong with the rig control feedback it is pretty obvious! > > 73 > Bill > G4WJS. > > > ------------------------------------------------------------------------------ > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
------------------------------------------------------------------------------
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
