You’re allowed to enter milliseconds. I also tested it locally and it works.
Which version are you using?
Another idea:
When you saved the preset, what exactly did you do? Typed a new name or clicked on an existing one?
If it’s the latter, then you just loaded that preset instead (it’s our fault of course)
yes that’s exactly the issue thanks.
So you should be instead retaining the context that the user launched the “save as preset” window, and replace that preset I click that I want to overwrite… not re-loading the preset.
@conor there is a long running debate around presets management. Some of us maintain that the old school OS provided file open/save dialogs are a much better option than the current “presets management” system that, in the view of some, causes more trouble than it solves.
Personally the current system causes too much grief for me so I don’t use presets at all and only save settings when I’m reporting bugs.