SRL Archive - SRL Suggestions

Why does SRL use OCR for IsUpText?

GetUpText with Pos

why not just IsTextInArea

IsTextInArea > OCR right?

Or am I missing something?

They are all using OCR in the end, no?

From: Harry
They are all using OCR in the end, no?

Technically it's not OCR unless it's reading the text instead of looking for specified text.

Edit: Can't believe I actually found this http://villavu.com/forum/showthread.php?t=56538&highlight=use+countcolor

I think you can't use IsTextInArea because the uptext is semi transparent. Most likely I'm wrong though :p

If you create a TPA for a specific text, it won't work. as the spacing between the characters changes dynamically these days, a Font->Text->TPA would likely fail.

'r' followed by 't' sometimes has no space at all, effectively making them one character.
And characters randomly shift one pixel left or right. That's why GetText is used. (Although it can't take care of the 'rt' either)
I assume you're running into this problem now?

E: So, technically, IsTextInArea has to perform a GetText as well.

Was just curious why a GetText was used vs FindText when one is more memory intensive and less reliable than the other.

It seems like there's the option for random spacing in FindText but that has never worked properly.

The 'rt' thing is another issue entirely.

I'm sorry, but I think that the 'rt' issue directly relates. The reason we use GetTextAt for the UpText is because it is so variable in spacing. (Something that also causes the 'rt' issue). For other things like Chat Text, the text is ``stable'', so TPAInTPA would work fine.

FindText is not reliable at all for Uptext, that is why GetText is used. But if you have a a good example + (open/sample) implementation I'd be interested.

It relates, but what I was getting at was the use of OCR when I thought it wasn't needed since the text being searched for was known.

I guess UpText has a lot of randomization in the spacing and my understanding of FindText's variable spacing is clouded as I've never gotten it to work correctly and I have no idea what was the difference between what I learned originally in SCAR being changed in simba, or if anything even was changed.

I supposed even with variable spacing in FindText working for UpText it would be just as memory intensive.

I'm writing a lot of text functions right now for RS2 and am running into a lot of questions like these.

I think it would benefit if I posted about it here so anyone who knows anything can say something for us all to know about.

I'll post what ever findings I can

I'm not quite sure if this is related, but I've had some issues using 'IsUpTextMultiCustom' (which apparently uses GetUpText, for what it's worth) and it has some issues reading uptext with a bright background behind the text. Have either of you come across something like this before?