sikuli-driver team mailing list archive

[RaiMan <question680137@xxxxxxxxxxxxxxxxxxxxx>]

Question #680137 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/680137

    Status: Open => Answered

RaiMan proposed the following answer:
yes, onChange should only start, when you have a stable screen
situation.

... but it must look so:

def changed(event):
        print "something changed in ", event.region
        for ch in event.getChanges():
                ch.highlight() # highlight all changes
        wait(2)
        for ch in event.getChanges():
                ch.highlight() # turn off the highlights
        event.repeat(5)

r = Region(Region(1056,312,26,30))
r.onChange(50, changed)

wait(2)
r.observeInBackground();wait(FOREVER)

... meaning you have to delay the observerstart

waiting in the handler does not make sense (except of course for the
highlight delay), because everything already happened (like
evaluating/filling the changes)

you talked about 4 seconds repeat frequency, now you have delay of abot
7 - 8 seconds in total (higlight + repeat)

-- 
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.