sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #48968
[Bug 1797985] Re: [1.1.4] Screen.newRegion() should return a Region object --- fixed 2018-10-17
Thanks for the pointer.
You are right: if it is there, it should return something useable ;-)
Was not aware, that this is of any use for local screens (they are bound
to a screen by the coordinates anyways). It is needed for non-local
Screens (like VNCScreen, ADBScreen) to create Regions from coordinates
and bind them to the the non-local screen objects.
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1797985
Title:
[1.1.4] Screen.newRegion() should return a Region object --- fixed
2018-10-17
Status in Sikuli:
Fix Committed
Bug description:
As it seems only Screen.newRegion(Location,width,heith) works.
As it seems also from the code
at line 454
@Override
public Region newRegion(Region reg) {
return null;
}
or line 476
@Override
public Region newRegion(int x, int y, int w, int h) {
return null;
}
I presume that a line similar to 451 is needed.
Lines are from SikuliX1/API/src/main/java/org/sikuli/script/Screen.java
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1797985/+subscriptions
References