Hi Alejandro,

the process-changed-only feature is for the moment for text creation only. Binary recreation is allways full project.

For the commit the tool I mentioned offers two menu items which will create *.??2 files and (auto) commit. Additonal items deal with manuell text or binary creation for several scopes of projects. As pointed out before, I'm not into automatic binary creation. For my work style it's not productive.

The zip at VFPX is with documentation, sourcecode visible inside the documentation. Docu is found at Bin2Text\Doku\pdm\index.htm in the package.

Simply I check the binaries via hashing for a change. Then I check the timestamps of the classes and create only changed. I guess whole VCX's for the moment, but this can be tweaked.

You might look into doku for bin_2_text.vcx class cusstorage methods filestoprocess,sync_file, check_vcx, check_scx

>Hi Lutz,
>
>Following Craig's and your advice I won't store the VFP bin files in the git repository.
>
>Being a forgetful fellow, I would like to automatically sync the generated text files (*.sc2, *.vc2 etc) with their corresponding binaries before every commit and after every checkout, merge etc.
>
>In your documentation you mention that your code optionally processes only files changed, comparing files checksums. Can you explain more please?
>
>Thank you very much.
>
>Alex
>
>
>>I'm with Craig. Exclude all binaries except that not transformed. Fernandos code works like a spell, no need to store those binaries.

Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off
There is no place like [::1]