Bill,
When I wrote, “delete the storage of the current configuration,” I meant the named configuration that was presently being used as the current configuration. Once I have CurrentConfig = UserConfig1, can’t I delete UserConfig1 and keep CurrentConfig? And thanks for the explanation of the configuration reset command – new information not otherwise available. Could we add that to the next documentation release? Ed. From: Bill Somerville <g4...@classdesign.com> Sent: Sunday, October 4, 2020 12:55 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] 2.3.0-rc1 UI on adding a new configuration Ed, what you describe is simply not possible. WSJT-X has to have a current configuration, if you want to delete the current configuration then another must become current. If you don't want the current configuration and you don't want to switch to another then all you need do is reset the current configuration, that will shift all settings to defaults, as if you had installed WSJT-X for the first time, with the exception that any other configurations you have created will be preserved. 73 Bill G4WJS. On 04/10/2020 17:47, j...@comcast.net <mailto:j...@comcast.net> wrote: Bill, It's not true that, "[i]f you no longer want a configuration then you surely are going to select a different one." I delete configurations regularly -- at the end of a DXpedition or contest, for example -- without a desire to switch to some other configuration at that moment. It's just housekeeping, so that the number of saved configurations does not grow without bound. At a club station that I visit, due to member turnover, changing interests, and equipment changes unused configurations are deleted frequently. If I delete a current configuration, I expect the program to delete the storage of the current configuration and remove the current configuration name from the pull-down configuration list and the status bar at the bottom of the main window, but otherwise do nothing detectable to the user -- it's just a configuration that is no longer selectable, so the user cannot return to the current configuration once he leaves it. If I delete the last remaining configuration, I would expect the program to operate as if the configuration feature did not exist -- i.e., it would stay with its present settings, but all future settings changes would have to be entered manually, as there would be no user-accessible memory of, well, prior settings configurations, until a new configuration was saved. 73, Ed N4II -----Original Message----- From: Bill Somerville <mailto:g4...@classdesign.com> <g4...@classdesign.com> Sent: Sunday, October 4, 2020 9:50 AM To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] 2.3.0-rc1 UI on adding a new configuration On 04/10/2020 11:23, Alan Groups wrote: One other thing - would be more intuitive if one could delete a configuration without having to open another one first! Alan G0TLK Hi Alan, I'm not sure I follow this request. If you no longer want a configuration then you surely are going to select a different one, OTOH if you want to reset a configuration to defaults you can do that whether it is the current one or not. If we allowed deleting the current configuration then which configuration should be substituted? What should the common edge case of only having one configuration and deleting it do? 73 Bill G4WJS.
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
