i didn't think that somebody has more than a couple of custom presets, so haven't implemented preset migration mechanism.
Actually I was just joking - while I have more than "a couple" of presets, rebuilding them again gave me a chance to fix a couple of grouping inaccuracies, so all good.
i'd uploaded the plugin several times during last night, maybe i've already fixed this bug.
Yep, that was it - seems to work now (odd, both versions were 5.7.8440). Isn't it some kind of programmer's sin to upload changes without modifying the build number?
i'll enlarge vertical size of preset list.
Maybe not enlarge it so much, just allow custom presets to sit "above" the default ones? I would think a user would be more interested in revisiting the ones they make themselves rather than the default/example presets (except at first, of course).
Speaking of lists, knowing how much people seem to be upset by little things, I might point out that the descenders are cut-off on the font used in the tag-selection list.
Lastly, as a suggestion, when creating a new preset, the "Save field to tag..." always defaults to <Date Created> for some reason. Wouldn't it be better if it defaulted to <Null> on the odd chance that someone creates a preset but forgets to assign this part properly then executes it? At least <Null> won't change anything accidentally.
I curiously seem to miss the old "Update/Save Preset" button, since making a preset is often a multi-stage thing, it was nice to be able to "save it" without actually having to "Save & Close" at the same time. I know that it doesn't really matter (it would all be saved at the end anyway), but I was so used to clicking that button that it's weird it's gone. Then again, I'm funny that way, so don't think too hard on it.