GetTextAtPoint returns nothing

[cshodges]

I had a script I made on a trial version that used GetTextAtPoint to make sure the mouse was at the right spot on a web page. Worked great.

Then I registered and upgraded to 10.1.02 and it just stopped working. Searching the forums revealed a different issue related to the same command: Known issue in 10.1: Some apps report error on exit

On a whim, I grabbed those old DLL's, and it fixed my problem too. GetTextAtPoint returns a value with the older DLL's, but only an empty string with the ones that come with 10.1.02.

Hopefully this is on the list to be fixed along with the other issue?

[Marcus Tettmar]

It's possible that it's just a coincidence - it is possible that the new DLLs failed to register when you installed the full version and changing them over freed things up. But we'll keep an eye out for any similar problems.

[Dman]

I'm using 10.1.15 and sometimes the GetTextAtPoint returns nothing.. reloading the application fixes it, but its an annoying bug..

[Marcus Tettmar]

This needs to be on the frequently asked questions list because I'm often answering this. I'll sort that.

Usually this is a timing thing, and GetTextAtPoint needs to be in a loop. The reason is that the app you are getting text from is not reporting it all the time, and the time you perform the GetTextAtPoint you may get nothing back. Run the Text Capture sample and point the mouse at the position and you sould see the text. The reason the Text Capture sample usually works where your script does not is that the sample script is running everything in a loop, so it keeps checking. So we often need to try something like:

Code: Select all

Label>wait_text
  GetTextAtPoint>x,y,text
  If>text=,wait_text

So the script keeps looking until it gets a result. Of course you could build a timeout into this if you want.

But first check with the text capture sample macro and see if you always get a result with that. If so it should work when you use a loop.