Thanks RaiMan for very quick response this is what we need to know once
again thanks for great product.
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1890138
Title:
Facing issue with Sikuli
use wait() instead.
This was a bad implementation in 1.x.
find() was always intended, to not wait for appearance, but search only
once.
** Changed in: sikuli
Status: New => Won't Fix
** Changed in: sikuli
Assignee: (unassigned) => RaiMan (raimund-hocke)
--
You received this bug
Question #692189 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/692189
RaiMan proposed the following answer:
@masuo: LOL - did not notice - very attentive :-))
--
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.
Question #692189 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/692189
Status: Needs information => Answered
masuo proposed the following answer:
@kai yung ezra chua
I think you only misunderstand shift + alt + c as shift + ctrl + c.
--
You received this question
Public bug reported:
Our objective is to be able to specify the timeout for the location of a
bitmap.
In early version of Sikuli i.e. 1.1.1 find() function internally calls
autoWaitTimeout() which wait's for stipulated time like if we overrides
the autoWaitTime by placing below code,
should first be a question
** Summary changed:
- Sikuli cannot be forced closed by shift+ctrl+c. huge bug
+ Sikuli cannot be forced closed by shift+ctrl+c
** Changed in: sikuli
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/sikuli/+question/692189
--
Question #692189 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/692189
Status: Open => Needs information
RaiMan requested more information:
what system?
what Java?
what version of SikuliX?
--
You received this question notification because your team Sikuli Drivers
is an
Question #692189 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/692189
Removed link to bug: #1890120
https://bugs.launchpad.net/bugs/1890120
"Sikuli cannot be forced closed by shift+ctrl+c"
--
You received this question notification because your team Sikuli
Question #692189 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/692189
RaiMan posted a new comment:
should first be a question
--
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.
New question #692189 on Sikuli:
https://answers.launchpad.net/sikuli/+question/692189
was testing the hotkey function and it wont let me force stop sikuli until it
finished the event (if i hold the hotkey down and queued too many events), only
way to preemptively stop it was to end task from
Public bug reported:
was testing the hotkey function and it wont let me force stop sikuli
until it finished the event (if i hold the hotkey down and queued too
many events), only way to preemptively stop it was to end task from task
manager. shift+ctrl+c DOES NOT work
script in question
def
11 matches
Mail list logo
