Question #678874 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/678874
Status: Open => Solved
RaiMan changed the question status:
The reason behind is the historical implementation of undotted Region methods:
- in the normal script they are dynamically (at runtime) bound to the constant
object SCREEN, which is globally initialised to Screen(0) (the primary screen)
- using with someRegion: they are bound dynamically to the given someRegion, by
dynamically assigning it to the object SCREEN.
I will not change anything here. If someone has a better implementation:
welcome as a pull request.
the same effect can be done by using
setROI(someRegion)/setROI(Screen(0)) or by using use(someRegion)/use().
I admit, that with: has some advantage due to the evident scope by the
block.
--
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.
_______________________________________________
Mailing list: https://launchpad.net/~sikuli-driver
Post to : [email protected]
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
