sikuli-driver team mailing list archive

[RaiMan <question264188@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
interesting.
I will support RFW a bit better than currently in version 2.

Your problem:
also planned for version 2: some more callbacks and internal checks that allow to pause/restart or abort a script.

only possibility in these usage scenarios (using SikuliX as library):
in the observe handler issue a Java System.exit() or any other means to stop the JVM.
If this does not work: do something, that lets the complete process crash (no idea though what).
Another possibility would be to use some reflection to get access to the top  driving Jython object and force it to terminate.
Same goes for some intermediate RFW objects in the call stack.

How can you signal RFW programmatically to terminate?

With version 1.1.0 the mouse usage can be coordinated between main and threads like observe in background.
There is already now a feature, that might pause/restart or abort a running script, when the mouse is moved manually to the left edge/top edge of the screen. But this feature needs Sikuli to be the top driver, which is not the case here.

But if you switch to version 1.1.0 and tell me what you need to stop RFW
from inside, I can help you to get it working or somehow support it.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.