SikuliX

lock up mouse(movement+click)

Asked by Dantel D

Hallo. Sikuli is a great project and it is fun working with it but there is something that bothers me and I wonder why noone else ever asked this question bevore (at least I couldnt find something similar over the search function).

Sikuli works pretty good but there is a big disadvantage making it pretty unstable for proper scripts: The mouse doesnt lock up when a script is running - so it is possible that the user will move the mouse during a critical period causing the whole script to "crash". So my question is - is there a way to lock up the mouse/keyboard during the execution of a script so the user cannot cause trouble by moving the mouse or other input?

If there is no standart for it in Sikuli - any suggestions to solve this matter?

Question information

Language:
English Edit question
Status:
Answered
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
RaiMan (raimund-hocke) said : 		#1

since there is something like the observer feature and it is possible to wait for something (using exists() e.g.) it is generally possible to have scripts that expect that the user is doing something while the script is running.

So I think to have it as a general option is something like wanting to run a sikuli script totally unattended on a system without any screen (there is a feature request bug)

so I suggest: make it a feature request bug.

To have a local solution for that:
Without having googled, I think there should be means available, to deactivate the mouse and even keyboard, run the script and then activate things again all this wrapped up in a command line script. But maybe this then makes it impossible to use the java robot any more - don't know.

Revision history for this message
Dantel D (anothermail2006) said : 		#2

Thank you for the response RaiMan.

>>So I think to have it as a general option is something like wanting to run a sikuli script totally unattended on a system without >>any screen (there is a feature request bug)

I dont agree with that. There are situations where you want the user to be able to do something and there are situations where you dont - just like in this case. The optimum would be a general option that can be switched on and off - in fact I believe that you dont want the user to be able to interrupt in most cases because you want things to be done automatically without any manual input (thats the main idea behind this project, isnt it).

Ive googled quite some time and didnt find a proper solutin until now.

Im thankful for every hint.

Revision history for this message
RaiMan (raimund-hocke) said : 		#3

Sorry, for being misunderstood:

I support your request for an option like that. I only compared it with the other feature request as being more general.

Since I am sure, Sikuli does not have such a feature in the moment, I suggested to supply a feature request bug additionally.

And then we have to wait for the developers ;-)

Revision history for this message
Dantel D (anothermail2006) said : 		#4

Oh I see, sorry :D. I created a bug report.

Still hoping there is someone who solved this matter with some additional software or something like that.

Revision history for this message
RaiMan (raimund-hocke) said : 		#5

Bug report created

Can you help with this problem?

Provide an answer of your own, or ask Dantel D for more information if necessary.

To post a message you must log in.