I just created a 7zip batch file and run it against my project which zips up my project and places in my dropbox directory so I have a history of what my project looked like at any given time.

It works well when I muck up my current version while I'm playing/testing/learning. I can easily go back to a previous version, and it's saved in the cloud just in case.

Just my 2 cents

Big Al

On 7/5/2017 2:57 PM, Tim Young [Elevate Software] wrote:
> What kind of backup are you referring to ?  A history of all updates to the source, or just a .bak containing the last edits ?

Tim,

I personally have found the bak solution to not really work for me
personally - i save all the time so bak would show very tiny differences.

source control works fine at OS level but getting one integrated would
be nice as well.

Alternative option would be to to have IDE events and ability to run
external command (or IDE plugin capability that has access to these
events) - so one could do something on "compile" or "build" or "deploy"
or "file close" or "project close"

Just an idea

Raul

Raul,

<< I personally have found the bak solution to not really work for me personally - i save all the time so bak would show very tiny differences. >>

Yeah, that's why I asked.  Personally, I have an Alt-F-S tick that I do out of habit when I'm thinking and have the editor open in front of me, so...

The editor *does* have all of the incremental changes performed on a given source file, so it's not hard to get and doesn't even involve performing diffs, but this will have to wait until I get a unified undo/redo in place that can handle the synched changes between both the form files *and* the source code.  Right now any automatic changes to the source units due to form designer/object inspector manipulations does not allow for automatic undo/redo.

I've just got to get over the 2.07 hump and then I can get a lot of these editor issues resolved.  It's all eminently do-able by mid-fall, I just need to put the pedal to the metal...

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

/*
What kind of backup are you referring to ?  A history of all updates to the source, or just a .bak containing the last edits ?
*/

Just BAK files would be sufficient.

In my situation, I had several units which I was stripping down to create the sample project and since EWB does not have timed saves (for now?), I would have been able to recover from the BAK files created the night before.

I still had not performed the compilation step yet before I realised that the files I were amending were not from the correct directory.

--
Frederick

<<.....you might like to look at something like AJC Active Backup. It takes copies all the time, and can recover intermediate versions that you haven't formally versioned. >>

Thanks for the tip, Matthew.  Looks pretty good.

= Steve

Tim Young [Elevate Software] wrote:

> I have an Alt-F-S tick that I do out of habit when I'm thinking and have the editor open in front of me

Me too. If .bak is implemented, please make it optional. Horrible to have a directory cluttered with junk. Unfortunately, another option means another path to test...

Perhaps the thing I'd prefer is to not keep the files locked against reading by other applications...

--

Matthew Jones

Matthew,

<< Me too. If .bak is implemented, please make it optional. Horrible to have a directory cluttered with junk. Unfortunately, another option means another path to test...  >>

Nah, I would do something historical that logged all versions.  BAK won't work for me, so....

<< Perhaps the thing I'd prefer is to not keep the files locked against reading by other applications... >>

I'm not sure what the heck is causing that.  All of the source files opened by EWB use share: deny-none.

Tim Young
Elevate Software
www.elevatesoft.com