Re: [Sikuli-driver] [Question #280523]: Captured images are grayed
Question #280523 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/280523 dinev posted a new comment: Same with 1.1.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] [Question #280915]: Auto generated images names causes a problem
New question #280915 on Sikuli: https://answers.launchpad.net/sikuli/+question/280915 In the new sikuli 1.1 there is a nice feature that automatically names your images. For example class screenDialog1: button_OK = If you put your cursor after "=" and take a image the name will aromatically generated -> button_OK.png That excellent idea however there is a problem In a bigger UI map you will definitely have more dialogues screen with different buttons... like this: class screenDialog1: button_OK = "button_OK.png" class screenDialog2: button_OK = now if you put your cursor on after "=" on the second button_OK and try to get image you will mess up your UI map without even knowing it. The problem is that sikuli will again generate "button_OK.png" and will replace the first one. There is no warning and even no visual change in in the first button until you reload sikuli. Suggested fix: - when image already exist just pop up dialogue for user to enter different name or - in old 1.0 sikuli there was automatic indexation 1,2,3 etc or - if you are in a class you may compose image name like this: screenDialog1.button_OK.png Neven ps: bug is logged here https://bugs.launchpad.net/sikuli/+bug/1529457 -- 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 1532541] Re: [1.1.0] Possible memory leak with Region objects in long running Jython scripts
Hey, RaiMan I just wanted to let you know I may have pinpointed the
issue of the no memory error - It seems to only do it when you save and
run after adding a new picture or changing code. (It may just be adding
new pictures, I'm not sure on this one!)
I caught onto this a little bit last night and did some tests and it
sure seems that it only crashes if you save your profile and run it
right after.
If you make changes to a profile and save and exit sikuliX completely
and reopen it before running everything is fine. If you save and run
right away, that's when you get memory issues.
I'm not sure if this is of any help to you, but I wanted to let you know
just on the chance it may help pinpoint the issue.
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1532541
Title:
[1.1.0] Possible memory leak with Region objects in long running
Jython scripts
Status in Sikuli:
In Progress
Bug description:
* for more information see the related question
I've been trying to make a script that looks for specific images, clicks on
them, and then clicks on the next button after that.
Currently, it does that - but it's incredibly slow, it can take up to two
minutes just to click on 4-6 images/buttons. Overall there are about 10 images
it's looking for all at once as they randomly pop up.
I've tried adding a region to my code to help speed it up but I couldn't
figure it out as I'm extremely new to even the most basic of script writing.
Below is the code I'm currently using:
while True:
Settings.ObserveScanRate = 18
Settings.WaitScanRate = 15
Settings.MoveMouseDelay = 0
Settings.MouseDelay = 0
CurrentBarRegion = ( Region(689,294,1059,685))
if exists (Pattern("1452165008359.png").similar(0.76), 0): hover
(getLastMatch())
if exists ("1452165060367.png", 0): click(getLastMatch())
There's about eight more if exists with pictures in it but that's the code.
Some thought as to why Sikulix is slow: all images are very similar with
light blue colors, seems Sikulix doesn't like light blue that much. Maybe the
method I'm using is bad and slowing down the process as well. Could try using
text search possibly, all buttons have big text in them.
Pictures are all high quality, my monitor is 24 inches, 1920x1080
resolution, lots of ram good CPU etc so it can't be due to that. If
anyone can help me speed up Sikulix by showing me how to put in region
properly or another method I'd greatly appreciate it. Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1532541/+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 #280903]: [1.1.0] java.lang.IllegalArgumentException: Cannot create PyString with non-byte value
Question #280903 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/280903
Status: Open => Answered
RaiMan proposed the following answer:
in Python strings the \ is an escape character and must be doubled if
used as a real character:
with open("C:\\error_log", "a") as f:
an alternative is to use so called raw strings, where every character is
real, but a \ must not be the last character:
with open(r"C:\error_log", "a") as f:
--
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 #280915]: Auto generated images names causes a problem
Question #280915 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/280915 Linked to bug: #1529457 https://bugs.launchpad.net/bugs/1529457 "Auto generated images names causes a problem" -- 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 #280915]: Auto generated images names causes a problem
Question #280915 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/280915 Status: Open => Solved RaiMan changed the question status: the discussion is in the related bug. -- 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 #280915]: Status of bug #1529457 changed to 'In Progress' in Sikuli
Bug #1529457 status changed in Sikuli: New => In Progress https://bugs.launchpad.net/sikuli/+bug/1529457 "[request] IDE: Auto generated image names using image = should not overwrite." This bug is linked to #280915. Auto generated images names causes a problem https://answers.launchpad.net/sikuli/+question/280915 -- 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 1529457] Re: [request] IDE: Auto generated image names using image = should not overwrite.
** Summary changed: - Auto generated images names causes a problem + [request] IDE: Auto generated image names using image = should not overwrite. ** Changed in: sikuli Status: New => In Progress ** Changed in: sikuli Importance: Undecided => Medium ** Changed in: sikuli Assignee: (unassigned) => RaiMan (raimund-hocke) ** Changed in: sikuli Milestone: None => 2.0.0 -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1529457 Title: [request] IDE: Auto generated image names using image = should not overwrite. Status in Sikuli: In Progress Bug description: In the new sikuli 1.1 there is a nice feature that automatically names your images. For example class screenDialog1: button_OK = If you put your cursor after "=" and take a image the name will aromatically generated -> button_OK.png That excellent idea however there is a problem In a bigger UI map you will definitely have more dialogues screen with different buttons... like this: class screenDialog1: button_OK = "button_OK.png" class screenDialog2: button_OK = now if you put your cursor on after "=" on the second button_OK and try to get image you will mess up your UI map without even knowing it. The problem is that sikuli will again generate "button_OK.png" and will replace the first one. There is no warning and even no visual change in in the first button until you reload sikuli. Suggested fix: - when image already exist just pop up dialogue for user to enter different name or - in old 1.0 sikuli there was automatic indexation 1,2,3 etc or - if you are in a class you may compose image name like this: screenDialog1.button_OK.png Happy holidays Neven To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1529457/+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 1529457] Re: [request] IDE: Auto generated image names using image = should not overwrite.
I will revise this feature in version 2.0 to have more options. I plan to support image groups, where a group is represented by an image folder. And the support for capturing images and organize them will be a separate app, so it can be used for all situations including the IDE. But for now you have to live with that "by design" effect: If you want to use this feature, you have to follow your own naming convention, to assure, that your images are not messed up. in your case: class screenDialog1: screenDialog1_button_OK = "button_OK.png" class screenDialog2: screenDialog2_button_OK = -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1529457 Title: [request] IDE: Auto generated image names using image = should not overwrite. Status in Sikuli: In Progress Bug description: In the new sikuli 1.1 there is a nice feature that automatically names your images. For example class screenDialog1: button_OK = If you put your cursor after "=" and take a image the name will aromatically generated -> button_OK.png That excellent idea however there is a problem In a bigger UI map you will definitely have more dialogues screen with different buttons... like this: class screenDialog1: button_OK = "button_OK.png" class screenDialog2: button_OK = now if you put your cursor on after "=" on the second button_OK and try to get image you will mess up your UI map without even knowing it. The problem is that sikuli will again generate "button_OK.png" and will replace the first one. There is no warning and even no visual change in in the first button until you reload sikuli. Suggested fix: - when image already exist just pop up dialogue for user to enter different name or - in old 1.0 sikuli there was automatic indexation 1,2,3 etc or - if you are in a class you may compose image name like this: screenDialog1.button_OK.png Happy holidays Neven To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1529457/+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 1532541] Re: [1.1.0] Possible memory leak with Region objects in long running Jython scripts
great thanks for the finding.
This surely helps, to at least get a point, where to start the
debugging.
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1532541
Title:
[1.1.0] Possible memory leak with Region objects in long running
Jython scripts
Status in Sikuli:
In Progress
Bug description:
* for more information see the related question
I've been trying to make a script that looks for specific images, clicks on
them, and then clicks on the next button after that.
Currently, it does that - but it's incredibly slow, it can take up to two
minutes just to click on 4-6 images/buttons. Overall there are about 10 images
it's looking for all at once as they randomly pop up.
I've tried adding a region to my code to help speed it up but I couldn't
figure it out as I'm extremely new to even the most basic of script writing.
Below is the code I'm currently using:
while True:
Settings.ObserveScanRate = 18
Settings.WaitScanRate = 15
Settings.MoveMouseDelay = 0
Settings.MouseDelay = 0
CurrentBarRegion = ( Region(689,294,1059,685))
if exists (Pattern("1452165008359.png").similar(0.76), 0): hover
(getLastMatch())
if exists ("1452165060367.png", 0): click(getLastMatch())
There's about eight more if exists with pictures in it but that's the code.
Some thought as to why Sikulix is slow: all images are very similar with
light blue colors, seems Sikulix doesn't like light blue that much. Maybe the
method I'm using is bad and slowing down the process as well. Could try using
text search possibly, all buttons have big text in them.
Pictures are all high quality, my monitor is 24 inches, 1920x1080
resolution, lots of ram good CPU etc so it can't be due to that. If
anyone can help me speed up Sikulix by showing me how to put in region
properly or another method I'd greatly appreciate it. Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1532541/+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 #280883]: How can I disable error logs in sikuli?
Question #280883 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/280883 masuo posted a new comment: I think there is that definition of the region somewhere in codes. Try to search for "Regin(0,940,1920,140)" in code file by Text editor. -- 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 #280903]: [1.1.0] java.lang.IllegalArgumentException: Cannot create PyString with non-byte value
Question #280903 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/280903
Status: Answered => Open
Karl is still having a problem:
That doesn't fix the error.
Even this produces the error:
with open("error_log", "a") as f:
f.write(“Success")
--
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 #280903]: [1.1.0] java.lang.IllegalArgumentException: Cannot create PyString with non-byte value
Question #280903 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/280903 Karl gave more information on the question: Is this related?: https://github.com/jythontools/jython/commit/c61eaefb774cdb174472265d3c27fc5b87febd34 -- 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 #280949]: Recognizing bad returns from Region.text()
New question #280949 on Sikuli: https://answers.launchpad.net/sikuli/+question/280949 I am using the region.text() function to get a string from a region that is constantly changing (a floating point number that changes every half second). Once the text is captured, I convert the text into a floating point number and do analysis on this number: for example: str = myRegion.text() myNum = float(str) myNum = myNum + 5.0 print myNum In most cases the capture works fine and I'm able to print out correctly. But in some iterations the text capture fails and the program crashes on the "myNum = float(str)" line because its trying to convert an invalid string capture into a float. I know the text() function is still in development but, does anyone have an idea of how I can do a check first to make sure the string has a valid float format before I do the conversion to a float value? I've tried playing around with the str.isdigit(), str.isalpha(), str.isspace() functions on the captured string first but they all crash when they try to check the invalid string. Thanks, Ken -- 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
