Suggestion for new feature- Improved 'downloading'

[Meraxes]

Ok this might sound trivial but it's becomming a pain in the arse...

I use Cosmos along with CTMod and a modified Telos SideBars add ons.

They all play very nicely together, and I've modified a few of the XML to place the bars and set options the way I like them... no problems there.

The problem comes in whenever I go to run the new version of cosmos updater.

First, It automatically updates when run , BEFORE you can even go into "configure"... Shouldn't you have a chance to configure your downloader BEFORE it starts it's work? Specifically that little 'clean interface' option.. I had it on the first time i installed cosmos, and wanted to turn it off after I modified my XMLs.. opened up the launcher, turned it off, but to my dismay it already had 'cleaned' out my other add-ons :(

Perhaps a simple button that says "Update Now" rather than autoupdate when you run the patcher?

The 2nd and more important suggestion is since this code is highly modifyable by the end user, it stands to reason that it WILL be modified at one point.. Any chance to get an option to turn on a 'confirm' dialog box whever it goes to overwrite or delete a file during update?

The status box at the end is nice to show what files it changed... but all too often that's already after the fact and too late to 'backup' any files you might have wanted to save.

If there were an option for users to turn on that would prompt every time it would overwrite a file "Warning- About to overwrite/delete C:\ProgramFiles\Wow\Interface\filexxx.lua" or something we could alt-tab, copy a backup (just in case) then come back and hit YES.. or NO as we choose.

As it is, I'm in the habit now of backing up my entire add-on directory each time I run cosmos's installer and then having to go back and figure out which XMLs i need to re-modify.

Meraxes

[sarf]

You can add <FILENAME.nopatch> files to the files directory to prevent that file from being patched.

The main reason for the patcher to work as it does is, as far as I know, simplicity and speed. People who have never used the Cosmos***** before might get befuddled if all it does is sit and never do anything.

The Cosmos***** does need some configurability, but it might be accomplished by adding -waitforupdateclick or other command line parameters instead of changing the default behaviour of the patcher.

Hopefully, the patcher will get more configurable as time passes.

Sarf
---
I'm sorry, I become inaudible when I am shy.

[Meraxes]

You can add <FILENAME.nopatch> files to the files directory to prevent that file from being patched.


Hmm.. ok that would work for now I suppose.. i can tell Cosmos to not patch any files I've updated manually..

But umm... "files directory" ? Which file's directory? (I assume you meant possessive file). The file where cosmos***** resides.. or the add on directory where the specific file I don't want patch resides? (ala C:\program files\wow\addons\myaddon\myaddon.nopatch ? )

[sarf]

The directory where the file that you do not want Cosmos to touch resides.

Sarf
---
The Bible contains six admonishments to homosexuals and three hundred sixty-two admonishments to heterosexuals. That doesn't mean that God doesn't love heterosexuals. It's just that they need more supervision.