The GGT File Comparison tool provides you with information on the differences between the local .xaml files in your project graphics working directory and the GGT graphics objects stored in the project’s SCT database. The tool matches corresponding files and database entries based upon file path and graphic object reference and then compares hash values generated from the XAML content of these. You may activate an external diff process (WinMerge) to compare XAML content directly.
The GGT tool matches local files by matching the filenames and paths between local files and subdirectories and SCT folders and graphic objects. Folder names and graphic names must match (case-sensitive) between the SCT graphics root folder and the local file graphics working directory. Graphic files that don’t match will show up as “Unmatched”.
One of the problems with the GGT tool is that is allows the user to edit graphics directly from the SCT or from local source files. The developer has to keep track of what file is getting modified and remember to save the changes to the other side as well. It is easy to forget which file has the newer updates.
Furthermore, if you deliver graphics to a site and graphics might be modified by other party, there is a potential for changes to the SCT that may allow graphic updates to get out of sync from the original developer’s source files. This tool will immediately identify these synchronization issues.