Is anyone else having issue with the method in the title? When the script reaches this area Windows 7 crashes. I've installed QTP 10 with patch. I also saw the same results with QTP 9.2 on Win7. The method works fine for XP.
I would not recommend using this unless you absolutely have to - it's not reliable enough no matter what. The best approach is having your development team (if possible) write code to support the WM_GETTEXT message in windows for the control in question.
Windows 7 and Windows Server 2008 R2 do not support the Windows API text recognition mechanism. Therefore, when you install the 00644 patch, the 'Use text recognition mechanisms in this order' option in the Options dialog box (Tools > Options > Text Recognition) is set to 'Use only OCR', and cannot be changed (the option is disabled).
[/ QUOTE ]
This is quite anoying.
What I want to know is what API text recognition mechanism QTP used to be able to use?
Why has microsoft broken this for us?
Does anyone except automated testers care about this?
I tried google on this issue but did not find any chatter about this except this interesting note from thebetaguy
[ QUOTE ]
In Windows 7, Microsoft will break from the Windows' norm by breaking previous API compatibility, offering new API frameworks as a native solution, and providing support for legacy frameworks (COM, ATL, .NET Framework, etc) through monolithic libraries designed to provide the functionality of all previous revisions of the modules in question.
[/ QUOTE ]
I wonder if Windows 7 does have legacy support for the mysterious removed "API text recognition mechanism"?