Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore viability of multi-density images as UI element identifiers - use this line #981

Closed
kensoh opened this issue Mar 21, 2021 · 4 comments
Labels

Comments

@kensoh
Copy link
Member

kensoh commented Mar 21, 2021

For eg, capturing screenshots on a high-density computer, and use in lower-density PC through a config option.

Ie downsize on the fly before execution. Otherwise computer vision matching will break on different screen densities.

Source - Telegram Group Chat

@kensoh kensoh added the feature label Mar 21, 2021
@kensoh
Copy link
Member Author

kensoh commented Mar 22, 2021

Adding on inputs from @1RedTea

Hi Kaushik, i just tried out a flow with different resolution and it works. Ken is spot on saving the higher resolution screen shot instead of a lower resolution Screenshot. I use PNG for all my Screenshot instead of Jpg. ☺️

@kensoh
Copy link
Member Author

kensoh commented May 25, 2021

Solution can be as simple as running below. Where 0.5 is the resizing that is done to provided input images.

vision Settings.AlwaysResize = 0.5

@kensoh kensoh changed the title Explore viability of multi-density images as UI element identifiers - to explore Explore viability of multi-density images as UI element identifiers - use this line May 28, 2021
@kensoh
Copy link
Member Author

kensoh commented May 28, 2021

Solution is take image snapshots at the computer with the 'largest' images. Note that big resolution doesn't mean large image. Because icon size will still be the same although there is a larger screen viewing and search area.

Probably this means taking image snapshots at the computer using the largest % zoom. For eg 125% zoom. Then to run on a computer with 100% zoom, set vision Settings.AlwaysResize = 0.8

If this works, to explore having an option in tagui_config.txt for easier usage instead of running that line for every robot.

@kensoh kensoh closed this as completed May 28, 2021
@kensoh
Copy link
Member Author

kensoh commented May 28, 2021

Above solution found from a similar problem at RPA for Python - tebelorg/RPA-Python#170 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant