Add History to Menu

Stamimail · 2017-11-20 14:58

It's good for cases you used recently one sets of rules, and close the program. Then, the next time, you open the program and you find you need the same sets of rules you just used recently.

Happen a lot when you missed files to rename, or find it's good for another folder/files needs the same rename you just used before.

den4b · 2017-11-21 18:33

Just to clarify, you are suggesting to keep track of recently used presets?

Stamimail · 2017-11-21 21:19

No, this is not related to presets at all, though it can help to make new ones.
I'm talking about the recent used renaming.
For example:
From (Current) task:
1 Rule: Insert, Statement: Insert "A" as Prefix (skip extension)
2 Rule: Insert, Statement: Insert "Z" as Suffix (skip extension)
To (Prev) task:
1 Rule: Delete, Statement: Delete from Position 1 until Count reaches 2 (skip extension)
2 Rule: Delete, Statement: Delete from Position 1 until Count reaches 3 (right-to-left) (skip extension)
3 Rule: Case, Statement: Capitalize every word (skip extension)

I'm thinking about Next/Prev buttons like this
https://snag.gy/NxBAJq.jpg.

How many tasks or how long (period) the history will be logged, this is really a question should be answered by experience.
I don't know how much I will page back to find a task I made in past.

Last edited by Stamimail (2017-11-21 21:28)

kunkel321 · 2017-12-07 21:12

+1 vote for the history buttons.

den4b · 2017-12-11 14:15

Then this is essentially an Undo/Redo feature for the rules table.

This can be implemented by storing snapshots of the rules table after every change, allowing user to go back and forth between these snapshots. However, this would capture every change, even marking or moving a rule. This won't allow you to easily jump between desired/usable setups, instead this gives you a fine control over undoing certain recent changes to the rules.

Presets, on the other hand, are designed for capturing reusable setups of rules.

Stamimail · 2017-12-11 19:14

Then this is essentially an Undo/Redo feature for the rules table.

Normally Undo/Redo are terms used for the current session, and unsaved when you close the program.
History will be there in the next startup of the program, and also will be there in the next restart of computer.
It needs to record the rules, when the user hit the green "Rename" button.

den4b · 2017-12-14 00:33

Stamimail wrote:

It needs to record the rules, when the user hit the green "Rename" button.

This functionality already exists - it is called "Save Preset". Just use it before hitting the "Rename" button.

Stamimail · 2017-12-14 08:29

"Save Preset" is good for future. For the next years.
"History" is good for going back to the recent jobs. (the last X jobs OR last weeks jobs), and mostly intended when you thought you were finished and closed the program without saving the preset for the time of current job.

Happen a lot when you missed files to rename, or find it's good for another folder/files needs the same rename you just used before.

Edit:

You can think about it like the difference in use in Internet Browser between:
1. Bookmarks (Save Presets)
2. History (Recent Presets)

People need them both.

Last edited by Stamimail (2017-12-14 10:31)

den4b Forum

#1 2017-11-20 14:58

Add History to Menu

#2 2017-11-21 18:33

Re: Add History to Menu

#3 2017-11-21 21:19

Re: Add History to Menu

#4 2017-12-07 21:12

Re: Add History to Menu

#5 2017-12-11 14:15

Re: Add History to Menu

#6 2017-12-11 19:14

Re: Add History to Menu

#7 2017-12-14 00:33

Re: Add History to Menu

#8 2017-12-14 08:29

Re: Add History to Menu

Board footer