The relevant changelog entries:
* Remember and restore the last used preset by the preset name, rather than via an anonymous default preset.
* The option to remember the last used rules/preset is enabled by default.
I've been meaning to implement this for a while now. Thanks for reminding. Will get right on it!
Stefan, the specification of a preset via the command line is like hard-coding to always load a particular preset. In contrast, the ability to remember and restore the last used preset will be a kind of an improvement of the already existing feature, where the relationship between the last used rules and the last used preset would be maintained between restarts.
I'm thinking of the following workflows:
1) Load a preset, close application. Start application, same preset is loaded.
2) Load a preset, change rules, close application. Start application, same rules are loaded but not the preset.
3) Load a preset, change rules, save preset, close application. Start application, same preset is loaded.
One could say, why not offer to save the modified preset before closing the application. Well, I'd like to take it one step at a time.
]]>isn't that already possible?
https://www.den4b.com/wiki/ReNamer:Command_Line
ReNamer.exe /preset <preset>
Load preset specified by a preset name or a full path.
Optionally, paths to files/folders can be appended.. ....
Just launch ReNamer from an shortcut (instead of ReNamer.EXE itself) where you have added that command line parameter.
]]>
But if I use a different set of rules (or edit the loaded rules), this cycle is interrupted.
It would be great if we can load a given preset when Renamer is launched.
]]>