[Sikuli-driver] [Bug 1890138] Re: Facing issue with Sikuli 2.0.4 version for find() function.
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 2.0.4 version for find() function. Status in Sikuli: Won't Fix Bug description: 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, sikuli_timeout = screen.getAutoWaitTimeout(); //it gives default time of Sikuli i.e. 3.0 sec screen.setAutoWaitTimeout(10); //Overriding autoWaitTimeout by setting 10.0 sec But in the latest version 2.0.4, find() is not calling the autoWaitTimeout due to which not able to override the default autoWaitTimeout. Please suggest how we can achieve this by some workaround. Sikuli version - 2.0.4 Operating System - 64-bit Windows Please check the find() method of Region.class of 2.0.4 and 1.1.1 and do comparison. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1890138/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1890138] Re: Facing issue with Sikuli 2.0.4 version for find() function.
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 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 2.0.4 version for find() function. Status in Sikuli: Won't Fix Bug description: 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, sikuli_timeout = screen.getAutoWaitTimeout(); //it gives default time of Sikuli i.e. 3.0 sec screen.setAutoWaitTimeout(10); //Overriding autoWaitTimeout by setting 10.0 sec But in the latest version 2.0.4, find() is not calling the autoWaitTimeout due to which not able to override the default autoWaitTimeout. Please suggest how we can achieve this by some workaround. Sikuli version - 2.0.4 Operating System - 64-bit Windows Please check the find() method of Region.class of 2.0.4 and 1.1.1 and do comparison. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1890138/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #692189]: Sikuli cannot be forced closed by shift+ctrl+c
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. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #692189]: Sikuli cannot be forced closed by shift+ctrl+c
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 notification because your team Sikuli Drivers is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1890138] [NEW] Facing issue with Sikuli 2.0.4 version for find() function.
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, sikuli_timeout = screen.getAutoWaitTimeout(); //it gives default time of Sikuli i.e. 3.0 sec screen.setAutoWaitTimeout(10); //Overriding autoWaitTimeout by setting 10.0 sec But in the latest version 2.0.4, find() is not calling the autoWaitTimeout due to which not able to override the default autoWaitTimeout. Please suggest how we can achieve this by some workaround. Sikuli version - 2.0.4 Operating System - 64-bit Windows Please check the find() method of Region.class of 2.0.4 and 1.1.1 and do comparison. ** Affects: sikuli Importance: Undecided Status: New -- 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 2.0.4 version for find() function. Status in Sikuli: New Bug description: 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, sikuli_timeout = screen.getAutoWaitTimeout(); //it gives default time of Sikuli i.e. 3.0 sec screen.setAutoWaitTimeout(10); //Overriding autoWaitTimeout by setting 10.0 sec But in the latest version 2.0.4, find() is not calling the autoWaitTimeout due to which not able to override the default autoWaitTimeout. Please suggest how we can achieve this by some workaround. Sikuli version - 2.0.4 Operating System - 64-bit Windows Please check the find() method of Region.class of 2.0.4 and 1.1.1 and do comparison. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1890138/+subscriptions ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1890120] Re: Sikuli cannot be forced closed by shift+ctrl+c
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
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1890120
Title:
Sikuli cannot be forced closed by shift+ctrl+c
Status in Sikuli:
Invalid
Bug description:
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 Handl(event):
type("1")
type("2")
Env.addHotkey(Key.F1, 0, Handl)
while True:
wait(0.1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1890120/+subscriptions
___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #692189]: Sikuli cannot be forced closed by shift+ctrl+c
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 answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #692189]: Sikuli cannot be forced closed by shift+ctrl+c
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 Drivers is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #692189]: Sikuli cannot be forced closed by shift+ctrl+c
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. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Question #692189]: Sikuli cannot be forced closed by shift+ctrl+c
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 task manager. shift+ctrl+c
DOES NOT work
script in question
def Handl(event):
type("1")
type("2")
Env.addHotkey(Key.F1, 0, Handl)
while True:
wait(0.1)
--
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.
___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1890120] [NEW] Sikuli cannot be forced closed by shift+ctrl+c. huge bug
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 Handl(event):
type("1")
type("2")
Env.addHotkey(Key.F1, 0, Handl)
while True:
wait(0.1)
** Affects: sikuli
Importance: Undecided
Status: New
** Description changed:
was testing the hotkey function and it wont let me force stop sikuli
- until it finishes the event, need to end task from task manager if i
- hold the hotkey down and queued too many events. shift+ctrl+c DOES NOT
- work.
+ 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
- code in question
+ script in question
def Handl(event):
- type("1")
- type("2")
+ type("1")
+ type("2")
Env.addHotkey(Key.F1, 0, Handl)
while True:
- wait(0.1)
+ wait(0.1)
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1890120
Title:
Sikuli cannot be forced closed by shift+ctrl+c. huge bug
Status in Sikuli:
New
Bug description:
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 Handl(event):
type("1")
type("2")
Env.addHotkey(Key.F1, 0, Handl)
while True:
wait(0.1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1890120/+subscriptions
___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
