Re: [Sikuli-driver] [Question #233740]: Sikuli Is Not Reading entire XML File
Question #233740 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233740 Status: Open = Answered RaiMan proposed the following answer: --- from xml.dom import minidom confirmed: there is some sort of problem with this import. But it only happens, when a script is run (either with Sikuli or with plain Jython). In interactive mode (Sikuli as well as Jython) it works. So it seems to be a Jython problem, but currently I cannot tell you why. Since I am currently busy with 1.0.1, I have no time to track this down. You might find out, wether there is another xml module, that you can use. --- HTML formatting problems in message area It is on the list, but with low priority. -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233740]: [1.0] Problems importing xml.dom.minidom in script running mode - interactive seems to work
Question #233740 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233740 Summary changed to: [1.0] Problems importing xml.dom.minidom in script running mode - interactive seems to work -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233740]: [1.0] Problems importing xml.dom.minidom in script running mode - interactive seems to work
Question #233740 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233740 Assignee: None = RaiMan -- You received this question notification because you are a member of Sikuli Drivers, which 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 1076372] Re: [request] improvement for run command
Thanks for contribution. I already fixed this with version 1.0.1, since I needed it myself internally ;-) The run() now handles parameters with enclosing apostrophes correctly, as well as the usage of \space and returns: stdout line1 stdout line2 stdout line3 ... *** error *** stderr line1 stderr line1 stderr line1 ... stderr exception message the error part is only appended if the err pipe has some content or the command execution forces an exception. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1076372 Title: [request] improvement for run command Status in Sikuli: In Progress Bug description: In GUI mode the run(command) should show the console window. In CLI mode the run(command) could optionally show the console window. Either way, it should check the exit code and either return it or fail. Without such improvement, it's just like submodule.call() To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1076372/+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 #233740]: [1.0] Problems importing xml.dom.minidom in script running mode - interactive seems to work
Question #233740 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233740 RaiMan posted a new comment: for the HTML text output this is a workaround: instead of print x use: print x.replace(, amp;).replace(, lt;).replace(, gt;) --- make a def or lambda to use it more often htmlEncode = lambda x: x.replace(, amp;).replace(, lt;).replace(, gt;) print htmlEncode(x) -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233740]: [1.0] Problems importing xml.dom.minidom in script running mode - interactive seems to work
Question #233740 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233740 RaiMan proposed the following answer: I fixed the HTML output problem with the version 1.0.1. You might try it already with the preview: faq 2269 -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233740]: [1.0] Problems importing xml.dom.minidom in script running mode
Question #233740 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233740 Summary changed to: [1.0] Problems importing xml.dom.minidom in script running mode -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233740]: Status of bug #1210472 changed to 'Fix Committed' in Sikuli
Bug #1210472 status changed in Sikuli: New = Fix Committed https://bugs.launchpad.net/sikuli/+bug/1210472 [1.0] IDE: HTML code not printed or not printed correctly in message area This bug is linked to #233740. [1.0] Problems importing xml.dom.minidom in script running mode https://answers.launchpad.net/sikuli/+question/233740 -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233740]: [1.0] Problems importing xml.dom.minidom in script running mode
Question #233740 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233740 Linked to bug: #1210472 https://bugs.launchpad.net/bugs/1210472 [1.0] IDE: HTML code not printed or not printed correctly in message area -- You received this question notification because you are a member of Sikuli Drivers, which 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 1210472] [NEW] [1.0] IDE: HTML code not printed or not printed correctly in message area
Public bug reported: --- fixed with version 1.0.1 - I'm trying to start file i/o in my program wanted to get a simple file read and print working. But sikuli isn't reading or printing the entire file. The file is a short xml file: ?xml version=1.0 encoding=UTF-8? flex loginFlex flexClient=https:///vsphere-client/#; username=r pwd=v/ /flex I've tried two ways of coding: from xml.dom import minidom xmldoc = minidom.parse(/Users/colej/Documents/loginFlex2.xml) print xmldoc.toxml() RESULT: ?xml version=1.0 ? second way import os myfile = open(/Users/colej/Documents/loginFlex2.xml) text = myfile.read() print(text) RESULT: ?xml version=1.0 encoding=UTF-8? [info] Exit code: 0 And ideas on why the ENTIRE file is not being read and printed??? Thank You! ** Affects: sikuli Importance: Critical Assignee: RaiMan (raimund-hocke) Status: Fix Committed ** Changed in: sikuli Status: New = Fix Committed ** Changed in: sikuli Importance: Undecided = Critical ** Changed in: sikuli Assignee: (unassigned) = RaiMan (raimund-hocke) ** Changed in: sikuli Milestone: None = 1.1.0 ** Description changed: + --- fixed with version 1.0.1 + - + I'm trying to start file i/o in my program wanted to get a simple file read and print working. But sikuli isn't reading or printing the entire file. The file is a short xml file: ?xml version=1.0 encoding=UTF-8? flex - loginFlex flexClient=https:///vsphere-client/#; username=r pwd=v/ + loginFlex flexClient=https:///vsphere-client/#; username=r pwd=v/ /flex I've tried two ways of coding: from xml.dom import minidom xmldoc = minidom.parse(/Users/colej/Documents/loginFlex2.xml) print xmldoc.toxml() RESULT: ?xml version=1.0 ? second way import os myfile = open(/Users/colej/Documents/loginFlex2.xml) text = myfile.read() print(text) - RESULT: + RESULT: ?xml version=1.0 encoding=UTF-8? [info] Exit code: 0 - And ideas on why the ENTIRE file is not being read and printed??? Thank You! -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1210472 Title: [1.0] IDE: HTML code not printed or not printed correctly in message area Status in Sikuli: Fix Committed Bug description: --- fixed with version 1.0.1 - I'm trying to start file i/o in my program wanted to get a simple file read and print working. But sikuli isn't reading or printing the entire file. The file is a short xml file: ?xml version=1.0 encoding=UTF-8? flex loginFlex flexClient=https:///vsphere-client/#; username=r pwd=v/ /flex I've tried two ways of coding: from xml.dom import minidom xmldoc = minidom.parse(/Users/colej/Documents/loginFlex2.xml) print xmldoc.toxml() RESULT: ?xml version=1.0 ? second way import os myfile = open(/Users/colej/Documents/loginFlex2.xml) text = myfile.read() print(text) RESULT: ?xml version=1.0 encoding=UTF-8? [info] Exit code: 0 And ideas on why the ENTIRE file is not being read and printed??? Thank You! To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210472/+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 #233740]: [1.0] Problems importing xml.dom.minidom in script running mode
Question #233740 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233740 Linked to bug: #1210474 https://bugs.launchpad.net/bugs/1210474 [1.0] Problems importing xml.dom.minidom in script running mode -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233740]: Status of bug #1210474 changed to 'In Progress' in Sikuli
Bug #1210474 status changed in Sikuli: New = In Progress https://bugs.launchpad.net/sikuli/+bug/1210474 [1.0] Problems importing xml.dom.minidom in script running mode This bug is linked to #233740. [1.0] Problems importing xml.dom.minidom in script running mode https://answers.launchpad.net/sikuli/+question/233740 -- You received this question notification because you are a member of Sikuli Drivers, which 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 1210474] [NEW] [1.0] Problems importing xml.dom.minidom in script running mode
Public bug reported: with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. ** Affects: sikuli Importance: Medium Assignee: RaiMan (raimund-hocke) Status: In Progress -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1210474 Title: [1.0] Problems importing xml.dom.minidom in script running mode Status in Sikuli: In Progress Bug description: with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210474/+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 1210474] Re: [1.0] Problems importing xml.dom.minidom in script running mode
Seems to be Jython problem, because it happens also, when using plain Jython to run a script containing this line. ** 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 = 1.1.0 -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1210474 Title: [1.0] Problems importing xml.dom.minidom in script running mode Status in Sikuli: In Progress Bug description: with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210474/+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 #233740]: [1.0] IDE: HTML coded text not printed correctly
Question #233740 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233740 Summary changed to: [1.0] IDE: HTML coded text not printed correctly Description changed to: fixed with 1.0.1 --- I'm trying to start file i/o in my program wanted to get a simple file read and print working. But sikuli isn't reading or printing the entire file. The file is a short xml file: ?xml version=1.0 encoding=UTF-8? flex loginFlex flexClient=https:///vsphere-client/#; username=r pwd=v/ /flex I've tried two ways of coding: from xml.dom import minidom xmldoc = minidom.parse(/Users/colej/Documents/loginFlex2.xml) print xmldoc.toxml() RESULT: ?xml version=1.0 ? second way import os myfile = open(/Users/colej/Documents/loginFlex2.xml) text = myfile.read() print(text) RESULT: ?xml version=1.0 encoding=UTF-8? [info] Exit code: 0 And ideas on why the ENTIRE file is not being read and printed??? Thank You! -- You received this question notification because you are a member of Sikuli Drivers, which 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 1210474] Re: [1.0] Problems importing xml.dom.minidom in script running mode
I again checked the problem with any combination of Sikuli and Jython 2.5.3 and 2.5.4: I do not get the error anymore. The only situation: if a xml.sikuli can be found in sys.path (might be in the same directory or even the current script), the import fails. Sikuli's import support prioritizes .sikuli scripts when searching along the sys.path, so a Sikuli script should not be named as a Python module, when this Python module should be imported. Nevertheless I leave this a s bug, to check wether this can be avoided somehow. ** Description changed: + --- problem + a Sikuli script xml.sikuli found on sys.path hides the Python module + --- + with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module - from xml.dom import minidom + from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1210474 Title: [1.0] Problems importing xml.dom.minidom in script running mode Status in Sikuli: In Progress Bug description: --- problem a Sikuli script xml.sikuli found on sys.path hides the Python module --- with a simple script like from xml.dom import minidom I get the following error File /Users/colej/Documents/xml.sikuli/xml.py, line 1, in module from xml.dom import minidom ImportError: No module named dom !!WHILE IMPORTING!! I did not find any method, to get minidom imported to use the minidom.parse... options. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210474/+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 #233331]: No parsers found error when running from command line
Question #21 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/21 Assignee: None = RaiMan -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233331]: No parsers found error when running from command line
Question #21 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/21 RaiMan posted a new comment: linked this question to bug 1210474, to have it together -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233331]: No parsers found error when running from command line
Question #21 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/21 Linked to bug: #1210474 https://bugs.launchpad.net/bugs/1210474 [1.0] Problems importing xml.dom.minidom in script running mode -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233667]: xlrd open workbook module not found
Question #233667 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233667 Status: Open = Answered RaiMan proposed the following answer: The folder to use must be: C:\Program Files (x86)\Sikuli X\Lib (it does not exist yet) ... and what you have to put there is the file xlrd.py you have to step down a bit into the package xlrd ;-) BTW: Sikuli has nothing to do with the C-based Python. The fact, that something works with Python is not really relevant. It might work with Jython or it might not work. And the Python stuff install procedures are not useable with Sikuli/Jython. -- You received this question notification because you are a member of Sikuli Drivers, which 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 512476] Re: the path to sikuli scripts can't contain non-roman characters
Also ü ö ä ß -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/512476 Title: the path to sikuli scripts can't contain non-roman characters Status in Sikuli: In Progress Bug description: confirmed on Windows, Mac. It seems Jython doesn't treat unicode characters correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/512476/+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 #233689]: Detect a dialog box
Question #233689 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233689 Status: Answered = Solved tlondon confirmed that the question is solved: Thank you for the responses folks. When preparing my images for RaiMan, I wanted to double check and make sure that larger images failed also. I did this so I could send my small images and larger images and say Both of these failed. As it turns out, the larger images worked without issue. I'm guessing my images were just too small - they captured only a part of a word (they weren't even the full height of a letter). As soon as I made them bigger it worked like a champ. Maybe that was my only problem? I'm not sure but for now I'm not experiencing this problem anymore. -- You received this question notification because you are a member of Sikuli Drivers, which 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 1210599] [NEW] Negative Target Offset causes an error message - Location outside any screen
Public bug reported: Version: Sikuli 1.0.1 OS: Windows 7 If you use a Target Offset on an image, when you mouse over or scroll over the code the following error message is display in the message window. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected Steps to reproduce 1. Open Sikuli 1.0.1 2. Use any command, ie click command and select something for the image 3. Click on the new image, Pattern Settings pop-up will open 4. Click on the Target Offset tab 5. Select a new Target, something to the left of the center. (The idea is to create a target offset with negative values) 6. Apply changes and close the pop-up 7. Now mouse of the new code. Expected Result: No error message should be displayed Actual Result: An error message is display whenever you mouse over or scroll past the code. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected ** 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/1210599 Title: Negative Target Offset causes an error message - Location outside any screen Status in Sikuli: New Bug description: Version: Sikuli 1.0.1 OS: Windows 7 If you use a Target Offset on an image, when you mouse over or scroll over the code the following error message is display in the message window. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected Steps to reproduce 1. Open Sikuli 1.0.1 2. Use any command, ie click command and select something for the image 3. Click on the new image, Pattern Settings pop-up will open 4. Click on the Target Offset tab 5. Select a new Target, something to the left of the center. (The idea is to create a target offset with negative values) 6. Apply changes and close the pop-up 7. Now mouse of the new code. Expected Result: No error message should be displayed Actual Result: An error message is display whenever you mouse over or scroll past the code. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210599/+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 1210599] Re: [1.0] Negative Target Offset causes an error message - Location outside any screen
Uuups just found it is still there ??? Nevertheless - I will fix it. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1210599 Title: [1.0] Negative Target Offset causes an error message - Location outside any screen Status in Sikuli: Fix Committed Bug description: Version: Sikuli 1.0.1 OS: Windows 7 If you use a Target Offset on an image, when you mouse over or scroll over the code the following error message is display in the message window. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected Steps to reproduce 1. Open Sikuli 1.0.1 2. Use any command, ie click command and select something for the image 3. Click on the new image, Pattern Settings pop-up will open 4. Click on the Target Offset tab 5. Select a new Target, something to the left of the center. (The idea is to create a target offset with negative values) 6. Apply changes and close the pop-up 7. Now mouse of the new code. Expected Result: No error message should be displayed Actual Result: An error message is display whenever you mouse over or scroll past the code. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210599/+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 1210599] Re: Negative Target Offset causes an error message - Location outside any screen
Thanks for finding: fixed in Service Update 1.0.1 (preview: http://www.sikuli.org/download.html) ** Summary changed: - Negative Target Offset causes an error message - Location outside any screen + [1.0] Negative Target Offset causes an error message - Location outside any screen ** Changed in: sikuli Status: New = Fix Committed ** Changed in: sikuli Importance: Undecided = Critical ** Changed in: sikuli Assignee: (unassigned) = RaiMan (raimund-hocke) ** Changed in: sikuli Milestone: None = 1.1.0 ** Description changed: + Version: Sikuli 1.0.1 OS: Windows 7 If you use a Target Offset on an image, when you mouse over or scroll over the code the following error message is display in the message window. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected Steps to reproduce 1. Open Sikuli 1.0.1 2. Use any command, ie click command and select something for the image 3. Click on the new image, Pattern Settings pop-up will open 4. Click on the Target Offset tab 5. Select a new Target, something to the left of the center. (The idea is to create a target offset with negative values) 6. Apply changes and close the pop-up 7. Now mouse of the new code. Expected Result: No error message should be displayed Actual Result: An error message is display whenever you mouse over or scroll past the code. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1210599 Title: [1.0] Negative Target Offset causes an error message - Location outside any screen Status in Sikuli: Fix Committed Bug description: Version: Sikuli 1.0.1 OS: Windows 7 If you use a Target Offset on an image, when you mouse over or scroll over the code the following error message is display in the message window. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected Steps to reproduce 1. Open Sikuli 1.0.1 2. Use any command, ie click command and select something for the image 3. Click on the new image, Pattern Settings pop-up will open 4. Click on the Target Offset tab 5. Select a new Target, something to the left of the center. (The idea is to create a target offset with negative values) 6. Apply changes and close the pop-up 7. Now mouse of the new code. Expected Result: No error message should be displayed Actual Result: An error message is display whenever you mouse over or scroll past the code. [error] Location: outside any screen (-64, 0) - subsequent actions might not work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1210599/+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 #233608]: Efficiency for Chess
Question #233608 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233608 Status: Answered = Open jay dee is still having a problem: Mr. RaiMan, let us jump further down this rabbit hole... I have a few more questions for you regarding this potential pathway. 1.) How fast does sikuli capture a 1920x1080 desktop screen capture ? No processing, just constant grabbing of screen and dumping the data into the same object over and over. What is the best speed one can achieve (perhaps in fps?) ? The reason for this would be to have real-time piece detection. I have reason to believe this is the slowest implementation. 2.) Otherwise, would having a simple change-was-detected method that triggers the pieceDetection method be better? I believe this might be so because the simple change method will not take as many cpu cycles. It's only when it detects a change on one of the squares will it call the more intensive method. 3.) I will be using sikuli for another portion of the project which will not be as crazy as a chess game. I am trying to implement it anywhere I can because the API is so easy. If this truly is too slow to be implemented then I will look at other options. Are there any other image processing libraries that may fit my purpose better for chess piece recognition? Sikuli has the best similarity compare with the fuzzy logic, its hard to beat. 4.) What is the difference between the regular sikuli and the exclusive sikuli java API ??? How is the java api 1.0.2 when the regular sikuli is not even 1.0.1 yet the java was released in 2012? Very confusing, this warrants an explanation please. What do I want to use for just strict java? Thank you for your time sir. -- You received this question notification because you are a member of Sikuli Drivers, which 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 #233667]: xlrd open workbook module not found
Question #233667 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/233667 Status: Answered = Open mach81 is still having a problem: Where exactly is xlrd.pyits not in the xlrd module folder -- You received this question notification because you are a member of Sikuli Drivers, which 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
