Portable Application Template 1.5 Suggestions

I think the DoAction, and Main sections, and maybe the InitVariables moved to the Init section mentioned.
I know the "average" user will just need to change the constants etc. at the very beginning.
This change is more for "intermediate" users who would want to add or change functionality, make it easier for them to follow the logic flow.
I've made several launcher using your template, but am at a point where I would like to add additional functionality. I'm not really familiar with NSIS and would have to figure out how to do it. But following the logic flow in your template makes it more difficult.
I realize the DoAction is reusing code for the backup and restore steps which is a more "proper" way to do it. But again for an "intermediate" user it would make customizing the script easier is the logic was top to bottom rather than modularizing for code reuse. If that makes sense.

Just to give you some ideas of what I want to do.
In one launcher I need to do a sting replace of the drive letter in some registry entries, but the reg file is in hex so I need to use a different plugin.
In another launcher I want to have it rename the settings directory but NOT copy the flash drive settings. Then at the end I still want it to copy any changes from the settings directory and restore the original.
It would be much easier for me (and I assume others) to do these kinds of customizations if the logic flow was top to bottom (old style top down programming)

For those who have fought for it, freedom has a flavor the protected will never know.

I did a quick read through, it looks good.
I will test it on several launcher, I can redo the ones I have done already.
I have only one "issue". If the backup directory exists, you delete it. I understand the rename won't work if it exists, but if it does exist, this means that a previous run didn't complete properly and the current directory is most likely the settings from the last portable run. By deleting the backup directory you are most likely deleting the original settings and renaming the previous portable files as the backup. Not sure how best to actually handle this "issue", possibly a prompt asking the user what to do.
In 99% of cases this shouldn't actually be an issue as the backup directory shouldn't exist, but in the event that it does, maybe the default action should be to delete the current directory instead and keep the old backup.
Anyone else have ideas on this?

-----------------------------------------------------------------------------------------------
For those who have fought for it, freedom has a flavor the protected will never know.

I redid 3 apps previously done with the 1.4 template.
the 1.5 template doesn't appear to be deleting the reg entries when the app closes.

-----------------------------------------------------------------------------------------------
For those who have fought for it, freedom has a flavor the protected will never know.

ok, I created a test app with test files and folders and test registry.
The files and folders aren't backed up.
If registry entry doesn't exist and data\Registry\RegistryKey1.reg exists it applies and deletes it correctly.
If registry entry exists and data\Registry\RegistryKey1.reg exists it backs up , applies, and restores correctly.
If registry entry exists but data\Registry\RegistryKey1.reg doesn't exist, it backs up and restores entries correctly but doesn not save changes to registry made while it was running.
If neither exist, entries added during application run are not saved.

-----------------------------------------------------------------------------------------------
For those who have fought for it, freedom has a flavor the protected will never know.

If the data\registry folder doesn't exist, it doesn't create it, so it fails to write the backup RegKey1.reg file.
If the data\registry folder exists, everything works as expected.
I haven't tested the new Yes,No, Cancel yet.

-----------------------------------------------------------------------------------------------
For those who have fought for it, freedom has a flavor the protected will never know.