On Mon, Feb 14, 2022 at 12:47 PM Julian N4JO <n4jo@...
No, not at all: everything you just typed (and what is in the manual) matches what I observe. What I found misleading is that I expected that any change I made to the setting in 4.2 to be saved on "Save Settings", but it isn't. If I change key speed in 4.2, exit the menu, and re-enter, my change looks like it's there, but if I "Save Settings" and go back into 4.2, what is actually in there is what was previously set using a single press of the left button, which is not the focus of the change I just attempted to make.
In other words, i.m.o. having the ability to change keyer speed in 4.2 is misleading if that value is never retained on "Save Settings". I would have expected that value - given that it is in a menu and editable - to be saved on "Save Settings" (which it isn't), and I would not have expected it to be overridden by the current value on "Save Settings" (which it is). I notice that "Save Settings" saves the current VFO settings too, so your philosophy is consistent, though you have the additional complexity of presets to deal with there.
The reason this came up at all is that when I return a unit to a customer, I go through the menus, reset everything to reasonable/your default values (and replacing my call and Maidenhead Locator with those of my customer in the beacon settings for their convenience, for example), and do a "Save Settings". That includes setting the keyer speed back at 12 WPM (or whatever they had it set to, if I remember), because when I test, I test at my preferred speed, which is 18 WPM. After doing a box-up and re-test, it surprised me that the boot-up keyer speed was back to 18 again, even though I thought I had set it to 12 while going through the menus.
I'm not arguing that it's wrong, it's just the way I think of it, that's all. (I think of the single button press value as being volatile in both ways: to be reset upon boot, and not to be saveable.) I guess I just don't remember it being the way it is... not that that means anything ;-)
No worries: if it behaves the way you intended, and it works in 1.08+ the way it always has, I have no issue.