Thanks for the update Greg. As for editing on both sides, that is mainly to use directly from Vault (Vault launches it). You cannot choose which file is left and which is right on the fly when passed from Vault (you set it under the diff setup and it's always the same until changed) so it would be nice to be able to edit either side (or to have a button above each editbox to make either side not readonly (one or the other would probably suffice but both at the same time is ideal) and have the save code in place on both sides)

Do you have another download that has the changes you mentioned below? I do not see it in 1.1...

I will gladly put the code in place so it can be called from Vault (and the two versions pushed into it) if you wish.

>Hello--
>
>Glad that you find tis tool useful. As to your questions:
>
>Is there a newer version that resolves these issues:
>
>1) Ability to resize the treeview on the left-hand side (basically make it wider like we can re-size the two edit boxes)
>This is available in the class/form comparison editor.
>
>
>2) Ability to edit either (left or right) side file (not just the left)
>Have not implemented; however, it would not be that hard to do. The class that provides the right side (which is read-only) is set by my choice and is the same class as the left side. The only additional part would be the logic to save the two files separately (both could be edited but only one is decided to be saved...). I might be able to implement this over the next few weeks -- no promises... Just curious, my original thought in making the right side read-only was that this side would the 'base' to compare to. Why change both?
>
>
>3) Ability to jump to a file in the directory popup window (from the ellipses buttons on the open file dialog) by pressing A-Z (i.e. press C and jump to files that start with C...)
>This is available now in all file open dialogs.
>
>So right now you have two of the above three... I have not released generally the changes that have been made since the last post to the UT. There have been many changes over the last year of all the tools/editors and I have been using to test/debug in order to try to 'squash' all problems before releasing.
>
>Also, the code that you use for the entry point (in order to support the repository) you would need to re-apply. I have not incorporated this work that you did -- so I can provide you with the source code again if you like.