Hi,
Since you start TestComplete as a COM server, I suggest that you consider changing the server registration records in the Registry to include the needed option to the server command line. For example, for a 32-bit version of TestComplete 12 on a 64-bit system, the Registry branch would be this:
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{990BBECC-B5F4-478C-9E90-1758B3CE814C}\LocalServer32
You need to change the (Default) key in that branch to include "/tr_prefer_wmpaint_hooking" to the command line:
"C:\Program Files (x86)\SmartBear\TestComplete 12\Bin\TestComplete.exe" /tr_prefer_wmpaint_hooking
See the attached screenshot.
There is a tricky thing though with this approach - TestComplete restores the COM server registration on start to the default state. So once it starts, it removes the parameter. So, in your logic that starts TC via COM, you'll need to implement an extra preparation step that modifies the Registry record before instatiating a new TC instance.
Would this work?
