Replied 28 January 2019, 12:39 am EST
I am not well versed with how UFT 14.0.3 works.
Taken from an old conversation with developer I can tell you that Spread COM supports the standard OLE automation interface IDispatch and can work with window automation tools like that -- usually they provide some limited API for scripting mouse click here, this key down/up, etc. and Spread should work fine with that, though it might be tricky to track edit mode and the cell editor control (that gets shown/hidden as needed when the user edits cells). If the tool provides a way to call the control's OLE automation interface, then it should be able to get access to the whole API exposed by the type library, including the events (if the scripting model supports that).
But Spread doesn't provide any special interface at the window level for such automated testing tools (the DLL control and core window code I mean) - it's only the ActiveX controls that have the OLE automation support and IDispatch implemented. So unless the tool has some way to do like you can in C++ with CWnd::GetControlUnknown, there might not be any way to access the automation interface from the windows handle (HWND). In C++ it's done like this:
I believe, the source of Spread COM is written in C++.