| QUOTE (Lil Devil @ December 24, 2013 02:50 pm) |
| Change that to a "greater than" comparison. |
I like this idea, and suspect we could get most macro authors to conform to a straightforward numbering convention that will work. x.xx (which I think most of us use) will work if it is evaluated as a real number.
| QUOTE |
| Last thought: when an automatic update is performed, keep a copy of the previous macro. Instead of overwriting, first rename oldmacro.gsk to oldmacro.backup20131224.gsk (or whatever) then write the new macro file. That way if something is inadvertently upgraded, there is a fallback. |
I have an "Old Versions" sub-directory of my macros folder that I save the current version of a macro to before I make any significant changes. If I release a new version and it has significant bugs, I can quickly revert back to the earlier version (if I decide to toss the new version before releasing it, I can restore the old version from the macro library).
However, neither your idea of renaming the file or my backup folder helps if you've put significant work into a macro and it then gets overwritten with the earlier version stored online, which is what sbeelis is worried about. To prevent that, I'll usually save the version I'm working on with a "-Beta" name suffix to prevent it from being updated from the online version. Then you just have to remember to rename it before posting the new version online.
