Checking the star there doesn't seem to do anything different. I can access the objects, but they all show as UIAObject instead of WPFObject, so, for example, if I have a WPF ComboBox, I only get the standard UIAObject wrapper methods to use on it (e.g. Click) instead of the WPF ComboBox wrapper methods (e.g. ClickItem).
Champion Level 3My understanding is that TestComplete loses the ability to inject its WPF hooks properly. At that point, it falls back to Microsoft UI Automation. I don't think it can expose WPFObject when WPF is hosted via ElementHost and the host is embedded in a non-dotNet container. It's like WPF is effectively "sandboxed" from TestComplete’s WPF plugin.
