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
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
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.
___
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
___
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
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
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
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:
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
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
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
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
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
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
27 matches
Mail list logo
