Confusing XClickTextRelative results stepping through a simple macro

I don’t see any options for previewing the forum entry I’m creating with images, so I’m submitting it with its screen captures without having seen how clear the screen captured images appear. A preview button would be a nice thing to have. Maybe that should go on a wish list somewhere…

Here’s a screen capture of the macro in question. I think this is easier to comprehend than its XML:

It seems to be correctly identifying the text I’m seeking, which is “Skip”. There are two targets IDed, each with its own confidence number, and the higher of the two is the correct match I’m seeking:

0.74 #1 is Skip, and 0.64 #2 is Spon. Since I’m stepping through the macro, it stops on step number 8, on the desired discovery of the desired text.

However, I was expecting it to have clicked the spot—it didn’t send a click. Was I supposed to have declared the type of click desired: left, right, single, double? Was it NOT clicked because it the macro was being stepped through? Did it not click because there were two possible results offered and needs a confirmation first, before it goes and does its own clicking?

Off Topic Question: Why, if I’m searching for text in XClickTextRelative, does clicking the “Select” button in the line in the macro trigger a crosshairs and require a click and drag of the screen (which would seem like an image selection thing), instead of triggering an arrow pointer that highlights the different fields it finds underneath the arrow pointer, to suggest and let me choose which text string I’m seeking?

To the team at UI.Vision and anyone else who’s doing to hard work to answer questions like these in the forum: THANK YOU!

You have a typo in your macro → It should be XClickRelative not XClickTextRelative!

What XClickTextRelative does is using OCR to look for the text mpvy_dpi_106.png not the image!!

Of course, since you want to click the word “Skip” anyway, do you not have to make a screenshot of the text. You can use the text directly with

XClickTextRelative | Skip

Or maybe use

XClickTextRelative | *Skip* to account for spaces before/after the word.

Thank you, I’ll try this. The learning road for this is easy but REALLY long.