Whenever i try using NM.GetElement and instead of using the virtual click i set it to false the clicks never work and if i animate the mouse it clear why:
The mouse cursor is always positioned way above to the left of the wanted element. And we are not talking pixels we are talking 10-20cm.
No neither is the case.
The Windows.GetElement works fine its just the NM.GetElement that has the problems. And its not an iframe and the selector itself works fine virtual clicks work fine:
ONLY physical clicks with NM Selector click somewhere else.
Highlight also needs to find physical location, so yes, those should always give the same result.
I find it very odd if NM is always wrong .. can you please doublecheck you didnt by mistake zoom in, in chrome ?
if you see this icon in the url bar, you are zoomed in
Then my best guess is either you changed zoom (in some other way ? not sure if that is possible), or you have an chrome extension installed that “messes” with the pages ?
could you try disabling all extensions except OpenRPA to test ?
I honestly could not remember if this was for all or only some, so I did a small test.
For me, highlight/physical clicks work fine if I set the zoom to both 125% and 150% for Windows.GetElement on a virtual machine. But it breaks with Chrome and Java when the zoom is not 100%.
I had to restart both OpenRPA, Chrome, and Edge every time I changed DPI settings to validate this.
Ok i can confirm that DPI Zoom was active on 125% by default. I Set it to 100% and now the highight and click is more accurate but, depending where i place the window its either on the button or slightly next to it. I can play with the offset to make it work but i am scared it will break on a different machine.