I'm not sure if you guys knew this but you can hook up scripts in 'FileHamster Advanced' that can be executed automatically or optionally; the optional setting places a 'run script' button in the FileHamster revision bubble so the user can simply choose when to execute the script by clicking on the button at revision time; FileHamster can use just about anything as a script but I've mostly just used common Windows batch files.
I thought this post relevent to the recent thread about having a tool that could either auto commit or optionally commit because you could hook up a commandline script to trigger your control commits. Using enviroment variables, you can customize the script to work dynamically and commit the recently modified file into your primary version control solution.
FileHamster's Script feature is quite extensive; In addition to just triggering a script, a user can actually pause, enable or even configure FileHamster through command files:
Here's a link with more information on the script commandline interface:http://wiki.mogware....ommandline_Interface
*The environment variables that can be used within a script are listed at the bottom of this web page.
We've used this kind of control in past projects to disable FileHamster ( by simply copying a 'disable command file' to the root of a project's directory prior to a sync or get latest ) so we could prevent FileHamster from revisioning the files as they were being being updated.