Hasan, I’m sorry, but I totally disagree. Configurations are there to switch e.g. between 2 completely different hardware setups, but not between two modes (or bands). Come on! That is the most basic task of a multi-mode program itself.
It is a pity that on this reflector EVERY suggestion for improvement is immediately discredited. Rather frustrating! That’s why the "clones" are more and more are growing in popularity ... The point is that in case of the new modes FST4, Q65, etc., a user cannot simply switch to the mode and get started (as it was with FT8, FT4, JT9, JT65, etc.) but first has to find out and put in the correct sub and sub-sub parameters, and has to do that every time he switches between these modes. No wonder that there are only VERY few users… (Here in EU the five or six stations using FST4 had QSOs with each other (or missed them because of sub-mode mismatch), and due to missing success they went back to FT8.) But all similar questions or comments from other users on that were also rejected. Sad story… 73 de Uwe, DG2YCB Von: Hasan N0AN [mailto:[email protected]] Gesendet: Dienstag, 16. Februar 2021 15:18 An: WSJT software development Betreff: Re: [wsjt-devel] Please save the T/R sequence lengths for each mode separately It looks to me that's precisely why Configurations were created. Why reinvent the wheel? People should learn to use configurations and they can then customize their ops in any way they like. I have 12 configs, every mode has its own config. No mistakes, no forgetting, no mis-setting. ...and no code bloat. 73, N0AN Hasan On Tue, Feb 16, 2021 at 6:39 AM Bill Somerville <[email protected]> wrote: Uwe, your description of your amendment sounds different from what you are asking for. If you have a version that switches to the T/R periods *you* use with certain modes, then that is fine for you but it is definitely not a general solution. if you have a general solution that you have tested for all modes and usage scenarios then why not contribute a patch? 73 Bill G4WJS. On 16/02/2021 12:27, DG2YCB, Uwe wrote: Hi Bill, Why are you not open to such a solution? Would certainly help to increase the extremely small number of FST4 users. It takes too long to switch configurations. But: I've already found a solution for myself. In my wsjt-x_improved versions, I have now programmed it so that the mode buttons automatically switch on the most common sub-mode (FST4-A60 or Q65-A30). Only needed two additional lines in the source code ... 73 de Uwe, DG2YCB Von: Bill Somerville [mailto:[email protected]] Gesendet: Dienstag, 16. Februar 2021 11:39 An: [email protected] Betreff: Re: [wsjt-devel] Please save the T/R sequence lengths for each mode separately On 16/02/2021 10:16, DG2YCB, Uwe wrote: Hi Bill, Please let wsjt-x save the T/R sequence lengths for each mode separately. Why? Because for FST4 on 160m, FST4-A60 seems to become something like a “standard”, and for Q65 on 6m Q65-A30. But as wsjt-x currently saves only one T/R sequence lengths setting, each time the users have to change T/R sequence length when switching from FST4 to Q65 mode. It would help a lot when for FST4 and Q65 individual values are remembered. (And let FST4-A60 and Q65-A30 become the default settings when switching to “FST4” or “Q65”, so that it is easier for less-experienced users to start with these new modes.) Only a very minor change, but a significant improvement. Thanks! 73 de Uwe, DG2YCB Hi Uwe, rather than undertake such a change I will recommend that you try using configurations to change mode, that way you can set the required T/R period along with other settings per mode, and even have multiple configurations for each mode you use, each with customized settings. 73 Bill G4WJS. _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
