X9 crashes using clip trimming handle

[Davidk]

Update after visiting grandkids for a week . . .

Synopsis: all went well, after re-install a check of that fort project file and trimming the clip (once) using the handles, did not crash the program when the mouse button was released. Previously, that was absolutely consistent once the mouse button used for trimming was released. The details are:
I noted the version number then uninstalled X9, using windows programs and features page, select X9 and rtclick, uninstall. When the panel opened, I checked (tick) the remove personal settings option box, and proceeded. That personal options box seems to be the Users\documents\x9 path that Trevor outlined, because after the uninstall was over, a check for that folder showed it did not exist.

Also confirmed that the folder where X9 had been installed was now empty (all files removed - not in re-cycle bin, but removed).

Cleaned up using cclean, and again noted the many many leftovers of X9 in the registry before removing them. Ran the X9 cleanup tool, and noted that although X9 was "gone" that tool found some leftovers too. 8 or 9 items, some msi files etc. I commented about that apparent need for a cleanup tool a year or so ago, because the normal/recommended uninstall processes of windows just don't seem to get it all.

Re-boot, and downloaded the X9 64bit main program only using the stub installer. Took the precaution of re-naming the old folder and creating a new one for the download first.

Stared the install using setup, and it all went normally. Completed, and before anything else, checked the start profile - ie, double click the desktop icon to verify start. And it did: same version - 19.5.0.35. Then installed the content pack and bonus features from previously (last Feb16) download files.

Configured X9 with various preferences and setting I use, and opened the fort project file for the acid test. Scrolled to the clip that was the subject of the original post, and using the LH trim handle dragged the handle some distance, and released. Waited . . . no stopped working message, VS still working after more than the previous fail time, so undid the change and (relieved), closed.

So, something had corrupted the program. It did not look like it, and the same installation happily opened and trimmed clips in other project files whilst the reporting was going on. What made me suspect some sort of program corruption was that the X9 install on my class laptop handled the same suspect project file without an issue. Several days of to and fro to verify that before my earlier re-install post.

Many thanks to Trevor for his suggestions . . .

Davidk