Feature request: use user presets in command-line renderer

[Edited after further testing]

I discovered this in updating my Filter Forge Batch Wrapper.

General steps to reproduce; this is with Filter Forge 7 and the included command-line renderer, and found that this behavior apparently goes back to at least Filter Forge 4:

- Use any filter
- Create a new user preset. I find that it saves a new file named after the original filter XML file to C:\Users\<my username>\AppData\Roaming\Filter Forge 7\My Presets (and that if I create another new preset, it updates that file with more <Preset... />.. XML. I'm curious what the purpose of that file is: does the GUI use it to load user presets into the available presets slot?
- Suppose the original filter came with 9 presets, and the user preset you added was a new, 10th one. If you create a command line render batch that uses preset 10 and run it, it fails to render anything, I assume because it's not locating "preset 10" (as you would think it would be from the Filter Forge user interface).

A workaround for this is to edit the filter and change nothing, then save it as a custom (new) filter. This saves the new preset (even if you added it before editing and saving the filter) to the custom filter itself, and the command line renderer finds it.

Okay, thanks.