sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #34310
Re: [Question #270538]: Is there a way to remove the sikuli import feature in the nightly build?
Question #270538 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/270538
RaiMan posted a new comment:
Thanks for staying with this issue - very helpful.
I have to admit, that I was not aware of the problem.
Up to 1.0.1 there indeed was an __init__ in class Region at the Python level.
With version 1.1.0+ the class Region at the Python level is only still
there, to stay backwards compatible on 'with someRegion:' and the
support for the undotted usage of Region methods (which then are bound
automatically to the primary screen).
So to keep things simple for you and others, I am trying to understand your approach.
I am testing with the latest 1.1.0 using Jython 2.7
actual problem:
testing with
class BaseClass(Region):
def __init__(region, name, sikuli=sikuli, lookup=None, curDir=None):
super(BaseClass, self).__init__(region)
I get the error:
[error] NameError ( global name 'self' is not defined )
which based on my Python understanding is inevitably
So what is your trick to have this working?
-- Are you saying that instead of the BaseClass using super().__init__(region) it should be using Region.init(region)?
this might be a possible solution, but a Region.init() does not exists yet.
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.