Contributions
What is the difference in the MSAA object handling when using "backwards compatible" mode or not?
Hi, we are currently trying to use MSAA object support in TestComplete; unfortunately the only way we seem to be able to get MSAA-enabled objects to show up as such is to enable the checkbox on the MSAA configuration page that allows "work with MSAA objects in mode compatible with TC 6 or earlier". What we would like to know is: how exactly is this method different from the more recent method, and how can we get the newer method to work with our program? We read the documentation, but unfortunately found only the standard examples of how to enable MSAA, which did not work fo rus unless we also set "backwards compatibility" mode.536Views0likes0CommentsWhy does TestComplete MSAA not seem to support error codes correctly?
Hi, we are currently trying to use MSAA in TestComplete to get the values from a list object in a GUI by first selecting it from the TC script and later reading the associated values. To enable this, the programmer implemented the IAccessible::accSelect method for this object; but while this method has a return value of type HRESULT, TestComplete does not show any error value when this method is called from a script with parameters outside of the range of the list. The result shows up as "undefined". Do you have any idea why this could be, or how we could get the correct error code as the return value for this operation?584Views0likes0CommentsTestComplete crash at the end of testing
Hi everyone, we are currently using a TestComplete script running on a TestExecute machine to test an application. This application is a Delphi program that uses .Net assemblies through COM. Recently we noticed a problem: when the tested application is closed at the end of the test run an exception occurs that apparently can be traced back to the TestExecute program: […] EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 00007ffd9d9910fb (oleacc!AccWrap_Base::Release+0x000000000000006b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000057b88e0 Attempt to read from address 00000000057b88e0 LAST_CONTROL_TRANSFER: from 00007ffda1122c7b to 00007ffd9d9910fb STACK_TEXT: 00000000`0023e4b0 00007ffd`a1122c7b : 00000000`0023e600 00007ffd`a10f208b 00000000`28e34e00 00000000`28c85260 : oleacc!AccWrap_Base::Release+0x6b 00000000`0023e4e0 00007ffd`a1122a1b : 00000000`06101838 00000000`28e34e08 00000000`28e34e00 00000000`28c0b63b : combase!ReleaseCallback+0x1b 00000000`0023e510 00007ffd`a1122978 : 00000000`28e34e08 00007ffd`a1122c60 00000000`26a66030 00007ffd`a117e4f0 : combase!PerformCallback+0x413 00000000`0023e5c0 00007ffd`a1122cb9 : 00000000`28cd9470 00000000`28c0b63b 00000000`2aca62e8 00000000`28cb8dc8 : combase!CObjectContext::InternalContextCallback+0x120 00000000`0023e6c0 00007ffd`a1122c24 : 00000000`06064520 00000000`26a66030 00000000`28cfe020 00000000`28e34e08 : combase!CGIPTable::RevokeInterfaceInCurrentApartment+0x105 00000000`0023e760 00000000`28b9d24f : 00007ffd`a127dd48 00000000`28cde890 00000000`00000000 00000000`00000000 : combase!CGIPTable::_RevokeInterfaceFromGlobal+0x128 00000000`0023e7e0 00000000`28b9d414 : 00007ffd`a127dd48 00000000`28cb79a0 00000000`28cfdfe0 00000000`28e34dd0 : tcMSAAAppHook+0xd24f 00000000`0023e820 00000000`28b9d3d2 : 00000000`00000000 00000000`00000000 00000000`26dbb1f0 00000000`2ace03f0 : tcMSAAAppHook+0xd414 […] (Complete call stack available if needed) Do you have any idea what could cause this behaviour or how to avoid it?1.3KViews0likes2Comments