Relation between code / apply / preset save unclear

[gmatters]

Is your feature request related to a problem? Please describe.

It is unclear what the relationship is between presets and code, whether presets are updated on [apply], how to "quit without saving" a preset, and how to update a saved preset. There is no "new preset" so I start with one of the examples and change the code. Does "apply" modify the example preset? I changed the name and description and saved my preset successfully. Later, I modified my preset and saved again. Now I have two different presets with the same name but slightly different code.

This confusion is amplified because presets are necessary in order to get back the code you used to write a kernel, if you need to modify it.

Describe the solution you'd like

There should be clear actions for "save as..." with a new name and "save" to update a previous preset. Possibly presets with identical names should be disallowed.

In my opinion, the plugin state should include the code, so that it is always possible to look at the glsl which is producing the output you are seeing. Then, presets could be an optional process of copying code back and forth between the plugin state and a named, saved copy.