I hadn't settled on a firm scheme for presets on the last build, so in my case it didn't much matter as I am redoing all my presets now anyway. But with the depth and complexity of presets needed to do what I'm now doing (having multiple buttons cycle through different settings or dialogs, each of which requires its own preset) it would be unimaginable to have to rebuild those presets every time I upgrade firmware. So I'm happy to hear that that's not supposed to be the case and that most presets SHOULD transfer with no problems between successive builds.
I still think that the ability to edit a preset already created is a glaring missing feature. It feels very primitive to have to remember exactly how you named a preset and then create a new one with the same name to overwrite it, all with no prompts to tell you you are about to overwrite an existing preset. But much more inconvenient than that is the situation where you revise your strategy as you go and realize that, for example, a custom cycle setup you created using multiple key mappings and presets for one key would also be useful duplicated to another key on another component (e.g., duplicating the setup for SH button A to LCD button top). Instead of just editing each preset to include new key mappings for the LCD button, you have to redo EVERY preset from scratch and add all the key maps at once to the same preset. That's where editing a preset could really save time.



