I've seen several posts on this problem: you edit a file, but Vault doesn't mark the file as modified. You close the Vault Client and reopen it, and the change set now notices the edited files.
My question is: Is the pending changeset problem somehow related to the program you use to edit the file? A few posts have insinuated that it is, but I'd like confirmation from a SourceGear person. I'm using Borland C++ Builder to edit the files in question, and Vault Client 2.0.4.
Also, if this problem is related to the program used to edit a file, is SourceGear planning to address this issue on the Vault end? Or is it something that would have to be fixed with each of the offending editors?
edits not put in pending changeset
Moderator: SourceGear
The problem does show up with certain editors. Vault depends on Windows to notify it of changes in the filesystem. Windows tells us which kind of modification happened (file copy, modification, move, delete, etc.), and if the file that was modified appears in our tree, we examine it to see what its status should be.
Some editors save a file "foo" by opening "foo" for writing (even it if already exists) and writing the new data. Other editors will open "foo~.bak" (or some other name) for writing, write the data, close the file, and move it over "foo". Still others will delete "foo", then rename "foo~.bak" to "foo". Each of these techniques generates a unique sequence of notifications that Vault receives.
This seems to work well with most editors, but a few (Microsoft Word with RTF, Wise Installer's editor, and maybe now Borland's editor) save with a sequence that trips up Vault. We'll try to find better techniques for recognizing these modifications in future versions of Vault. As a workaround now, you can check out the files before editing them. This will cause Vault to examine the files more often during normal operation for status (it couldn't examine every file in all working folders efficiently, but it can do the list of checked out files).
Some editors save a file "foo" by opening "foo" for writing (even it if already exists) and writing the new data. Other editors will open "foo~.bak" (or some other name) for writing, write the data, close the file, and move it over "foo". Still others will delete "foo", then rename "foo~.bak" to "foo". Each of these techniques generates a unique sequence of notifications that Vault receives.
This seems to work well with most editors, but a few (Microsoft Word with RTF, Wise Installer's editor, and maybe now Borland's editor) save with a sequence that trips up Vault. We'll try to find better techniques for recognizing these modifications in future versions of Vault. As a workaround now, you can check out the files before editing them. This will cause Vault to examine the files more often during normal operation for status (it couldn't examine every file in all working folders efficiently, but it can do the list of checked out files).
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`