Andy (and all): There's a thread, started by me a couple of days ago, about issues with the frequency tables under 2.6.0-rc5 on the WSJT-X forum on groups.io; you'll find the first message in the thread at:
https://wsjtx.groups.io/g/main/message/40301 As you'll see the issue I've reported relates primarily to what happens to the frequency tables when using and switching between different configurations, including one that I use for FT8 Hound operations. The very helpful response to my initial message from Brian N9ADG suggested a solution to the problem that appears to work, albeit needing a bit of time and effort to implement, but there still seems to be an issue with the frequency tables when starting WSJT-X with Hound mode enabled, as I do in my FT8 Hound configuration. 73 -- Martin G0HDB On Sat, 3 Dec 2022 at 15:34, Andy Durbin via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > If WSJT-X 2.6.0-rc5 is closed with FT8 active and Hound not selected it > restarts with standard frequencies available in the frequency selector. > > If Hound is selected the standard frequencies remain in the frequency > selector. > > If WSJT-X is closed and re-started then it opens with Hound active and the > Fox/Hound frequencies in the selector. > > If Hound is then deselected the Fox/Hound frequencies remain in the > frequency selector. > > If WSJT-X is closed and re-started then the standard frequencies are > restored to the frequency selector. > > If a restart is required to make the frequency selector consistent with > the active mode then having a Hound button seems to offer no advantage over > having a separate Fox/Hound configuration. The current implementation > seems likely to cause much confusion. > > 73, > Andy, k3wyc > >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
