First of all, once deleted, is the old build gone for good ? Doesn't seem to be in my trash folder.
Yes, because moving it into trashcan wouldn't save any diskspace; as I said before,
original SVN files can always be restored through "Unzip Archive..", if user wants to
modify a build,
cloning it first is strongly recommended - builds with a 'tail' (i.e. 'trunk1250_mymod') will never be purged.
Secondly, when you tell it to keep the last 5 builds, it counts backwards from the current build release number. So, for example, if you were working with version 1245 and didn't update for a while and then enable updates again when the trunk is at 1254, your 1245 version gets deleted !!
True - I'll look into improving this.
Is that the default after a version upgrade?
No, if an ini file exists which is no older than 10 versions of CHDK-Shell all previous settings should be imported (exception: some debug options)
Believe me, if it was possible to write protect 'original' SVN checkouts (to force user to clone before modifying source), I would have done that a long time ago, but that would make it impossible to compile said originals ...
So, for the moment I can only suggest to:
- If using the 'Remove old builds' always use 'Clone' when modifying or
- Not use 'Remove old builds' (or maybe set to a higher number)
Meanwhile, here's a '~!~purge.au3' replacement that 'deletes' to trashcan (see attachment)
Original line (DirRemove) commented out, new one (FileRecycle) added.
(the file is located in the /CHDK-Shell subdir)
Hope that helps a bit,
wim
PS Did I mention cloning is highly recommended before modifying source code ?