den4b Forum

Elektro

Senior Member

Registered: 2014-05-28

Posts: 76

New Rule: Run Preset

I'm gonna explain my situation as an example and as a reason of this suggestion,
so imagine that the enduser have a preset full of rules (lets say 50 rules) and another single preset for "other uses" with the same quantity of rules, and this user want to use both presets simultaneouslly in "X" cases, then by the moment the only solution I think is to duplicate all the rules from both presets to save them as a single third (ugly, weird) preset to use it, or another solution should be firstly load the first preset, use it, drag&drop again the files, load the second preset, use it.

So to save a very big amount of time, and honestly I think this is a very good feature not only for my case, for everyone that want to speed-up things adding rules faster or to do some tests mixing presets or whatever else reasons...
...I suggest to implement the usage of a rule that just should select an existing preset by its filepath to run/load the rules that contains that preset in "X" position of the preset where the imaginary rule "Load Preset" would be added.

Thanks for read!

Last edited by Elektro (2014-06-07 12:50)

Elektro

Senior Member

Registered: 2014-05-28

Posts: 76

Re: New Rule: Run Preset

What think about this suggest?

den4b

Administrator

From: den4b.com

Registered: 2006-04-06

Posts: 3,479

Re: New Rule: Run Preset

It's an interesting suggestion, but implementation is a bit problematic.

Did you know that you can easily append presents together in Presets Manager (Ctrl+P)?

---

A story of software development, and how it all evolves into Live vs Pro
Request a Wiki account | Reporting spam and abuse | Why did I get banned?

Elektro

Senior Member

Registered: 2014-05-28

Posts: 76

Re: New Rule: Run Preset

Did you know that you can easily append presents together in Presets Manager (Ctrl+P)?

Yes but it's not the same, when appending, all the rules of the appended preset are loaded into the current preset and this means static rules.

my idea is a little bit different, if I have a "preset1.rnp" it should append ONLY one rule "example: run preset > C:\preset2.rnp" and this has the advantage of non-static rules 'cause it just should look and interpret the current rules of that preset, not append a set of static rules into the GUI.

So this way, in "preset1.rnp" I could have a preset with this imaginary rule "run preset > C:\preset2.rnp", save the preset, and then I could open and edit the rules of the other "preset2.rnp" without worries, when I load into the program again the "preset1.rnp" it should load the rules that I have edited or added in the "preset2.rnp", but in a hidden way without filling the GUI with all those rules of the ran preset like the preset manager does (or maybe not? maybe a expandible treeview in the design when clicking the "run preset" rule to view the loaded rules should be very nice too, it's just an idea).

I hope this could be added in the future!! would be really amazing and (one more) distinctive feature that will never have other poor renamers!.

Thanks for read.

Last edited by Elektro (2014-06-29 04:00)