Editor: Versions Incremental AutoSave
As a NuB, I often end up with code with errors in it that I am not able to find the problems in and correct.
An adjustable background incremental AutoSave of series of versions would enable one to go back through the previous versions until one found the most recent version that works.
I do save different versions, but not every time a successful change is made. If the Editor saved the new version of the code EVERY TIME that changes had been made and complied successfully, it would overcome this problem.
There are obvious drawbacks to this: filling up ones HDD with hundreds of versions of ones MQ files etc. Settings that allowed users to turn this on or off. An adjustable FIFO stack of background versions being saved etc will handles this.
Perhaps this will help
http://www.visualsvn.com/server/
This is a simple to install and maintain svn server. If you are not acquainted with SVN, google it. There are many tutorials available.
investeo:
Perhaps this will help : http://www.visualsvn.com/server/
This is a simple to install and maintain svn server. If you are not acquainted with SVN, google it. There are many tutorials available.
Hi,
Thanks for the suggestion, but my computer is overloaded as is.
I don't run anything that isn't absolutely necessary.
At times 'Less IS More' This is one of them.
They are reworking v5 so now is the time to include it as a sensible option for everyone.
Being 'OverLoaded' applies to me as well. I don't need yet another learning curve needlessly.
That being said, don't take it personally. I DO appreciate your helpful suggestion.
Thanks (< 8)
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
As a NuB, I often end up with code with errors in it that I am not able to find the problems in and correct.
An adjustable background incremental AutoSave of series of versions would enable one to go back through the previous versions until one found the most recent version that works.
I do save different versions, but not every time a successful change is made. If the Editor saved the new version of the code EVERY TIME that changes had been made and complied successfully, it would overcome this problem.
There are obvious drawbacks to this: filling up ones HDD with hundreds of versions of ones MQ files etc. Settings that allowed users to turn this on or off. An adjustable FIFO stack of background versions being saved etc will handles this.