App.close() seem to nicely ask, which is good, but it should then forcefully terminate/kill the process.

An optional argument, or a App.terminate() or App.kill() may be possibly if an automatic terminate/kill after 15 sec or so seems wrong.

There's a small problem, NuGet, the underlying technology to Chocolatey, does not support the latest semver spec. Which would have us version the package like this

1.0.0-rc.3+build.905

However, NuGet will only support the old spec, with an arbitrary string appended

1.0.0-rc3build905

If you only publicly release incremented RC versions, then we can make it a little sexier

1.0.0-rc3

**** Known Problem (https://answers.launchpad.net/sikuli/+faq/1766)

**** Pls. report issues, bugs and questions at https://launchpad.net/sikuli

Mac OS X 10.6, Snow Leopard.

If you close the application with a .sikuli file already open then try to launch Sikuli IDE again, you will get an error dialog:

Cannot launch Java application Uncaught exception in main method: java.lang.NullPointerException

The application will not quit normally and must be killed with the Force Quit command.

Sikuli IDE can only be started again by overwriting the IDE_SESSION key from the preferences file before launching.

defaults write org.sikuli.ide '/org/sikuli/ide/' -dict-add "IDE_SESSION" -string ';'

There is the following code in region.rst:

def changed(event):
        print "something changed in ", event.region
        for ch in event.changes:
                ch.highlight() # highlight all changes
        sleep(1)
        for ch in event.changes:
                ch.highlight() # turn off the highlights
with selectRegion("select a region to observe") as r:
    # any change in r larger than 50 pixels would trigger the changed function
    onChange(50, changed)
    observe(background=True)

wait(30) # another way to observe for 30 seconds
r.stopObserver()

The usage of variable r looks weird: shall it be the following instead?

def changed(event):
        print "something changed in ", event.region
        for ch in event.changes:
                ch.highlight() # highlight all changes
        sleep(1)
        for ch in event.changes:
                ch.highlight() # turn off the highlights
with selectRegion("select a region to observe") as r:
    # any change in r larger than 50 pixels would trigger the changed function
    r.onChange(50, changed)
    r.observe(background=True)

    wait(30) # another way to observe for 30 seconds
    r.stopObserver()

Hi all

I am new to sikuli.

this tool very beautiful to test the gui i don't know the maven structure for sikuli if any one knows show the sample structure and pom

Thanks in advance Chelladurai.A

Chocolatey is a package manager for Windows. I've created a package that installs the portable Sikuli and puts an environment (x86/x64) specific link on the Desktop. I'd be happy to provide the spec/script file to your repo (so your team can own it).

It would be cool to have this tied into whatever build/publish system you've got going on in Hudson. But, basically, you just increment the version number in the nuspec file. Update the static zip path in the install script. And repackage and publish to http://chocolatey.org.

I can share information, helper scripts, etc with you.

The application I am testing has steps where sometimes the next step response time can be quick but sometimes it can take longer.

"wait(target, timeout)" is really useful as I can request to wait until target appears or until the maximum timeout supplied.

But I have observed that this function does not use the timeout supplied, instead waits until the auto wait timeout. I have actually verified this:

before setting auto wait timeout:- screen.wait(DATAMART_CREDENTIALS_LABEL, DB_CONNECTION_WAIT_TIME); FindFailed error occurs. As it waits for the default auto wait not the timeout supplied.

after setting auto wait timeout:- screen.setAutoWaitTimeout(DB_CONNECTION_WAIT_TIME); screen.wait(DATAMART_CREDENTIALS_LABEL, DB_CONNECTION_WAIT_TIME); Waits until the image is found as the auto wait timeout is longer than the default and hence runs successfully.

Can I request the team to kindly fix this issue as It would really be helpful if this function actually works.

Hi,

The java pattern.exact() suffers from a problem, it does not always match correctly the image at the screen. The Sikuli IDE works normally with the same image. I used similar(0.995f) to get the score and I noticed the match score returns numbers like 0.9999996423721313. I tried other images. I guess the problem is related with how python and java round the score number before checking the exists..

[]s, ricardo

Ok, straightened out my branch issue. Here's a changeset right on develop. Should close #7. I'll play with prerequisite install/configurations and if I find anything interesting, I can submit some docs (wiki? readme? build-win32.txt? any recommendations?)

Needs libvncclient Useful if you want to do something else with your mouse/keyboard while sikuli is running

Use it like...

vncscreenid=JScreen.connectVNC(["vncviewer","192.168.1.111"],"password")
vncscreen=Screen(vncscreenid)

# Then everything will have to be accessed via the new "vncscreen" object.

vncscreen.click(Location(1,1))
vncscreen.type("abc")
vncscreen.find("xxx.png")

In GUI mode the run(command) should show the console window.

In CLI mode the run(command) could optionally show the console window.

Either way, it should check the exit code and either return it or fail.

Without such improvement, it's just like submodule.call()