Consequences of enabling MSAA?
I've been working on creating some test code to run through our installer, but I've found that it doesn't work correctly unless MSAA windows are enabled (specifically, * is checked under Open Applications -> MSAA in the project properties).
I'm frankly a little confused about how all of this works. With MSAA disabled, I'm able to find the buttons I'm looking for in the object browser, but TestComplete just doesn't seem to be able to interact with them. I can fix it by creating a project with MSAA interaction enabled, but I'm a little concerned what the consequences of enabling this option might be. Will code that I've written while MSAA was disabled possibly encounter issues? What about UI Automation? I currently have UIA disabled, but given that MSAA and UIA seem to operate on some of the same controls, will there be a conflict between these two if I enable both of them? What if I have controls in the same project that require one or the other?
I wasn't able to find a thorough discussion of these topics in the TestComplete help files, so I apologize if I just missed it.
Re: Consequences of enabling MSAA?
Your code which doesn't use MSAA shouldn't cause any problems if you enable it. As for UI Automation, to avoid conflicts between UIA and MSAA, you shouldn't enable them both for all windows (the '*' option). Enable them for certain windows only if you need them both.