[Sikuli-driver] [Question #678844]: switchApp() is no longer functional

2019-02-27 Thread Renke He
New question #678844 on Sikuli:
https://answers.launchpad.net/sikuli/+question/678844

Yesterday I updated my SikuliX 1.14 to the latest build #211, my previous one 
was 2018-10-20_9:35 . I find the switchApp() is no longer functional. It use to 
works well but now it just won't do anything. Please help.

-- 
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 #678838]: Assertion failed _img.size().height <= _templ.size().height && _img.size().width <= _templ.size().width in function 'cv::matchTemplate'

2019-02-27 Thread Krisjanis Berzins
New question #678838 on Sikuli:
https://answers.launchpad.net/sikuli/+question/678838

Sometimes I get these errors:

org.opencv.core.CvException: CvException [org.opencv.core.CvException: 
cv::Exception: OpenCV(3.4.2) 
C:\build\3_4_winpack-bindings-win64-vc14-static\opencv\modules\imgproc\src\templmatch.cpp:1107:
 error: (-215:Assertion failed) _img.size().height <= _templ.size().height && 
_img.size().width <= _templ.size().width in function 'cv::matchTemplate'

Am I right in assuming they are to do with the region being too small or not 
fitting the image/pattern I am searching for when it is found? I think I am 
able to work around by extending/recapturing the region after which these 
errors stop. But I am not 100% certain.

-- 
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 #678837]: Region: findAnyCollect: image file not found:

2019-02-27 Thread Krisjanis Berzins
New question #678837 on Sikuli:
https://answers.launchpad.net/sikuli/+question/678837

I am getting these in my log file:

"[error (26/02/2019, 12:48:54)] Region: findAnyCollect: image file not found:"

I believe this might be happening during a while loop which runs both exists() 
and findAny() functions for hours at a time.

per thousands of iterations this error only shows up a few times.

Any suggestions on how to debug it?

-- 
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 1817962] [NEW] intermittent error j < nsrcs && src[j].depth() == depth

2019-02-27 Thread Krisjanis Berzins
Public bug reported:

I am trying to figure out this intermittent error that sometimes shows
up after the script has run for some time:

[error (27/02/2019, 17:38:38)] Error caused by: Traceback (most recent call 
last):
  File "C:\SikuliX\project.sikuli\project.py", line 884, in 
lookForExit()
  File "C:\SikuliX\project.sikuli\project.py", line 822, in lookForExit
if regionArrows.exists(arrRB,0.5) and Dir == "L":
]
at org.opencv.core.Core.mixChannels_0(Native Method)
at org.opencv.core.Core.mixChannels(Core.java:1740)
at org.sikuli.script.Finder2.makeMat(Finder2.java:494)
at org.sikuli.script.Finder2.makeMat(Finder2.java:477)
at org.sikuli.script.Finder.setScreenImage(Finder.java:144)
at org.sikuli.script.Finder.initScreenFinder(Finder.java:139)
at org.sikuli.script.Finder.(Finder.java:124)
at 
org.sikuli.script.Region.doCheckLastSeenAndCreateFinder(Region.java:2938)
at 
org.sikuli.script.Region.checkLastSeenAndCreateFinder(Region.java:2899)
at org.sikuli.script.Region.doFind(Region.java:2846)
at org.sikuli.script.Region.access$300(Region.java:21)
at org.sikuli.script.Region$RepeatableFind.run(Region.java:3109)
at org.sikuli.script.Region$Repeatable.repeat(Region.java:3060)
at org.sikuli.script.Region.exists(Region.java:2376)
at jdk.internal.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
org.opencv.core.CvException: CvException [org.opencv.core.CvException: 
cv::Exception: OpenCV(3.4.2) 
C:\build\3_4_winpack-bindings-win64-vc14-static\opencv\modules\core\src\channels.cpp:128:
 error: (-215:Assertion failed) j < nsrcs && src[j].depth() == depth in 
function 'cv::mixChannels'
]

This is running on Windows 7 64 bit
Standard SikuliX installation on 1.1.4 latest nightly build. No custom 
libraries or any fancy stuff. The "C:\build" does not exist on this machine, 
but not sure if that is a problem, it just refers to the original source file 
pre-compilation perhaps?

I've attached the image file thats being used in that search function.
Note that it was saved as PNG using Paint after it was cropped from the
original SikuliX captured file.

I don't see any other correlations with something else happening at the
time these errors are thrown. They seem fairly random to me.

Initial research suggest something to do with OpenCV mixChannels not
accepting the particular image format/colour depth or so on. But It
could be because something else of course?

** Affects: sikuli
 Importance: Undecided
 Status: New

** Attachment added: "image file used for the function in question"
   https://bugs.launchpad.net/bugs/1817962/+attachment/5242147/+files/arrR.png

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1817962

Title:
  intermittent error j < nsrcs && src[j].depth() == depth

Status in Sikuli:
  New

Bug description:
  I am trying to figure out this intermittent error that sometimes shows
  up after the script has run for some time:

  [error (27/02/2019, 17:38:38)] Error caused by: Traceback (most recent call 
last):
File "C:\SikuliX\project.sikuli\project.py", line 884, in 
  lookForExit()
File "C:\SikuliX\project.sikuli\project.py", line 822, in lookForExit
  if regionArrows.exists(arrRB,0.5) and Dir == "L":
  ]
at org.opencv.core.Core.mixChannels_0(Native Method)
at org.opencv.core.Core.mixChannels(Core.java:1740)
at org.sikuli.script.Finder2.makeMat(Finder2.java:494)
at org.sikuli.script.Finder2.makeMat(Finder2.java:477)
at org.sikuli.script.Finder.setScreenImage(Finder.java:144)
at org.sikuli.script.Finder.initScreenFinder(Finder.java:139)
at org.sikuli.script.Finder.(Finder.java:124)
at 
org.sikuli.script.Region.doCheckLastSeenAndCreateFinder(Region.java:2938)
at 
org.sikuli.script.Region.checkLastSeenAndCreateFinder(Region.java:2899)
at org.sikuli.script.Region.doFind(Region.java:2846)
at org.sikuli.script.Region.access$300(Region.java:21)
at org.sikuli.script.Region$RepeatableFind.run(Region.java:3109)
at org.sikuli.script.Region$Repeatable.repeat(Region.java:3060)
at org.sikuli.script.Region.exists(Region.java:2376)
at jdk.internal.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
  org.opencv.core.CvException: CvException [org.opencv.core.CvException: 
cv::Exception: OpenCV(3.4.2) 

Re: [Sikuli-driver] [Question #676299]: OpenCV exception can't be caught (out of memory) and kills JVM

2019-02-27 Thread Krisjanis Berzins
Question #676299 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/676299

Krisjanis Berzins posted a new comment:
Hello RaiMan,

Just wanted to chime in here - the C:\build\... is part of a non existing path! 
I don't even have a directory "build" on my C drive.
and I am getting many different errors all pointing to this misterious 
C:\build\... path and various different libraries all with extension .cpp

I am also using completely standard SikuliX setup since about version
1.1.0 and I can't say I noticed this before but on 1.1.4 on my current
project I am having headaches with this.

I promise I will open other separate bug reports for each issue I am
facing. Unfortunately there are many.

So, the problem is most certainly not anything to do with custom
libraries Paul is using, it has something to do with OpenCV or
implementation...

-- 
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 1817939] Re: [1.1.4] IDE: Warning: Unpaired quote characters in comments

2019-02-27 Thread RaiMan
** Description changed:

+ --- problem situation
+ This is related to the IDE option .
+ Comments are also checked for image file names, to avoid deletion of an 
image, that might not be used only temporarily (hence commented out, but should 
not be deleted).
+ The warning should be more declarative and should only come up if the 
situation is relevant.
+ 
+ 
  An unpaired single or double quote character in a comment raises a
  "Possible incomplete string" warning.
  
  To reproduce, create a small script:
  
  # don't do this
  
  Creates the warning, but only if the whole script is run. If only a
  selection (that contains the comment line) is run, the warning is not
  shown, even if the selection encompasses the whole script …
  
  Shouldn't anything in comment lines be ignored entirely (just like
  parentheses etc.) and not be checked for a matching counterpart?
  
  Anyway, this is just a VERY minor nuisance.

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1817939

Title:
  [1.1.4] IDE: Warning: Unpaired quote characters in comments

Status in Sikuli:
  In Progress

Bug description:
  --- problem situation
  This is related to the IDE option .
  Comments are also checked for image file names, to avoid deletion of an 
image, that might not be used only temporarily (hence commented out, but should 
not be deleted).
  The warning should be more declarative and should only come up if the 
situation is relevant.
  

  An unpaired single or double quote character in a comment raises a
  "Possible incomplete string" warning.

  To reproduce, create a small script:

  # don't do this

  Creates the warning, but only if the whole script is run. If only a
  selection (that contains the comment line) is run, the warning is not
  shown, even if the selection encompasses the whole script …

  Shouldn't anything in comment lines be ignored entirely (just like
  parentheses etc.) and not be checked for a matching counterpart?

  Anyway, this is just a VERY minor nuisance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1817939/+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 1817939] Re: [1.1.4] IDE: Warning: Unpaired quote characters in comments

2019-02-27 Thread RaiMan
** Summary changed:

- IDE: Unpaired quote characters in comments result in a warning
+ [1.1.4] IDE: Warning: Unpaired quote characters in comments

** 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.4

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1817939

Title:
  [1.1.4] IDE: Warning: Unpaired quote characters in comments

Status in Sikuli:
  In Progress

Bug description:
  An unpaired single or double quote character in a comment raises a
  "Possible incomplete string" warning.

  To reproduce, create a small script:

  # don't do this

  Creates the warning, but only if the whole script is run. If only a
  selection (that contains the comment line) is run, the warning is not
  shown, even if the selection encompasses the whole script …

  Shouldn't anything in comment lines be ignored entirely (just like
  parentheses etc.) and not be checked for a matching counterpart?

  Anyway, this is just a VERY minor nuisance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1817939/+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 1817939] [NEW] IDE: Unpaired quote characters in comments result in a warning

2019-02-27 Thread Rainer
Public bug reported:

An unpaired single or double quote character in a comment raises a
"Possible incomplete string" warning.

To reproduce, create a small script:

# don't do this

Creates the warning, but only if the whole script is run. If only a
selection (that contains the comment line) is run, the warning is not
shown, even if the selection encompasses the whole script …

Shouldn't anything in comment lines be ignored entirely (just like
parentheses etc.) and not be checked for a matching counterpart?

Anyway, this is just a VERY minor nuisance.

** 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/1817939

Title:
  IDE: Unpaired quote characters in comments result in a warning

Status in Sikuli:
  New

Bug description:
  An unpaired single or double quote character in a comment raises a
  "Possible incomplete string" warning.

  To reproduce, create a small script:

  # don't do this

  Creates the warning, but only if the whole script is run. If only a
  selection (that contains the comment line) is run, the warning is not
  shown, even if the selection encompasses the whole script …

  Shouldn't anything in comment lines be ignored entirely (just like
  parentheses etc.) and not be checked for a matching counterpart?

  Anyway, this is just a VERY minor nuisance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1817939/+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 1817853] Re: [1.1.3] findAll Fail

2019-02-27 Thread RaiMan
** Changed in: sikuli
   Status: Opinion => Invalid

** Changed in: sikuli
   Importance: Medium => Undecided

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1817853

Title:
  [1.1.3] findAll Fail

Status in Sikuli:
  Invalid

Bug description:
  1.1.3(2018-06-07_14:48)/Linux4.15.0-36-generic/Java8(64)1.8.0_191-b12
  v_Image2 = Pattern(v_Image).similar(x1)
  if exists(v_Image2,0.2) and v_test == 0:
  v_Pos  = find(v_Image2)
  hover(Location(v_Pos.x,v_Pos.y))
  v_Result = list(findAll(v_Image2))

  I added the find and hover to see if the find work - it did the error was on 
the findAll
  I have an image and I am looping on x1 to check what similiarity matches and 
how many many matches = len(v_Result) 
  [error] FindFailed ( 
/home/jeff/SikuliScripts_Linux/Subs/Vikings_Troops/Quantity Box.png: (4x11) 
seen at (221, 272) with 0.77 in S(0)[0,0 1366x768] E:Y, T:3.0 )

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1817853/+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 1817853] Re: [1.1.3] findAll Fail

2019-02-27 Thread Jeff_Vallis
Solved
In between 
hover and findAll 
I had a popup box with a message of what value the similar test "x1" was using
when I added a 5 second wait after the popup the findAll worked ok

Must be something to do with the script running faster than the refresh
as the popup was hiding the rectangle that I was testing

Removal of the popup - findAll works ok

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1817853

Title:
  [1.1.3] findAll Fail

Status in Sikuli:
  Opinion

Bug description:
  1.1.3(2018-06-07_14:48)/Linux4.15.0-36-generic/Java8(64)1.8.0_191-b12
  v_Image2 = Pattern(v_Image).similar(x1)
  if exists(v_Image2,0.2) and v_test == 0:
  v_Pos  = find(v_Image2)
  hover(Location(v_Pos.x,v_Pos.y))
  v_Result = list(findAll(v_Image2))

  I added the find and hover to see if the find work - it did the error was on 
the findAll
  I have an image and I am looping on x1 to check what similiarity matches and 
how many many matches = len(v_Result) 
  [error] FindFailed ( 
/home/jeff/SikuliScripts_Linux/Subs/Vikings_Troops/Quantity Box.png: (4x11) 
seen at (221, 272) with 0.77 in S(0)[0,0 1366x768] E:Y, T:3.0 )

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1817853/+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 #678626]: Switching off all currently active highlighting

2019-02-27 Thread Rainer
Question #678626 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/678626

Status: Answered => Solved

Rainer confirmed that the question is solved:
Thanks RaiMan, that solved my 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


Re: [Sikuli-driver] [Question #678800]: How to do screen comparison using sikuli ide?

2019-02-27 Thread Asheru
Question #678800 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/678800

Status: Open => Answered

Asheru proposed the following answer:
So you want to:
- navigate with browser A
-do some actions
-take a screenshot with sikuli
-store it in a constant like resultBrowserA = myScreenshot.png


- do the same thing for browserB
-resultBrowserB = myScreenshot2.png


compare IF resultBrowserA = resultBrowserB ?

IF you want something similar I guess you can use FInder class from
sikuli. See- http://doc.sikuli.org/finder.html

-- 
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 1817556] Re: [1.1.4] IDE: Toolbar buttons: crash if capture selection is drawn to another screen --- fixed 2019-02-26 build# 211

2019-02-27 Thread Mike
I'm only too pleased to be able to help. The impression I get is you
maintain Sikulix almost single-handed and that must involve a lot of
work. It would be better if the workload could be spread a bit more.

I am currently just a Sikulix beginner but will try and make more
contributions as my knowledge progresses.

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1817556

Title:
  [1.1.4] IDE: Toolbar buttons: crash if capture selection is drawn to
  another screen --- fixed 2019-02-26 build# 211

Status in Sikuli:
  Fix Committed

Bug description:
  observed on Windows 10 with the Offset button:

  Exception in thread "AWT-EventQueue-0" java.awt.image.RasterFormatException: 
(x + width) is outside raster
  at sun.awt.image.IntegerInterleavedRaster.createWritableChild(Unknown Source)
  at java.awt.image.BufferedImage.getSubimage(Unknown Source)
  at 
org.sikuli.util.OverlayCapturePrompt.drawSelection(OverlayCapturePrompt.java:334)
  at org.sikuli.util.OverlayCapturePrompt.paint(OverlayCapturePrompt.java:384)
  at javax.swing.RepaintManager$4.run(Unknown Source)
  … more
  [error] OverlayCapturePrompt: cropSelection: RasterFormatException

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1817556/+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 1817853] Re: findAll Fail

2019-02-27 Thread RaiMan
can you send me the image and a screenshot (sikulix---at---outlook---dot
---com)

** Changed in: sikuli
   Status: New => Opinion

** Changed in: sikuli
   Importance: Undecided => Medium

** Changed in: sikuli
 Assignee: (unassigned) => RaiMan (raimund-hocke)

** Summary changed:

- findAll Fail
+ [1.1.3] findAll Fail

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1817853

Title:
  [1.1.3] findAll Fail

Status in Sikuli:
  Opinion

Bug description:
  1.1.3(2018-06-07_14:48)/Linux4.15.0-36-generic/Java8(64)1.8.0_191-b12
  v_Image2 = Pattern(v_Image).similar(x1)
  if exists(v_Image2,0.2) and v_test == 0:
  v_Pos  = find(v_Image2)
  hover(Location(v_Pos.x,v_Pos.y))
  v_Result = list(findAll(v_Image2))

  I added the find and hover to see if the find work - it did the error was on 
the findAll
  I have an image and I am looping on x1 to check what similiarity matches and 
how many many matches = len(v_Result) 
  [error] FindFailed ( 
/home/jeff/SikuliScripts_Linux/Subs/Vikings_Troops/Quantity Box.png: (4x11) 
seen at (221, 272) with 0.77 in S(0)[0,0 1366x768] E:Y, T:3.0 )

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1817853/+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 1817556] Re: [1.1.4] IDE: Toolbar buttons: crash if capture selection is drawn to another screen --- fixed 2019-02-26 build# 211

2019-02-27 Thread RaiMan
great thanks for the systematic work and docs.

I have to admit, that I wrote down the workflow from memory (due to lack
of multi-monitor).

I leave this on my list to be revised again, when I can test it.

** Changed in: sikuli
   Status: In Progress => Fix Committed

** Changed in: sikuli
   Importance: Medium => Critical

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1817556

Title:
  [1.1.4] IDE: Toolbar buttons: crash if capture selection is drawn to
  another screen --- fixed 2019-02-26 build# 211

Status in Sikuli:
  Fix Committed

Bug description:
  observed on Windows 10 with the Offset button:

  Exception in thread "AWT-EventQueue-0" java.awt.image.RasterFormatException: 
(x + width) is outside raster
  at sun.awt.image.IntegerInterleavedRaster.createWritableChild(Unknown Source)
  at java.awt.image.BufferedImage.getSubimage(Unknown Source)
  at 
org.sikuli.util.OverlayCapturePrompt.drawSelection(OverlayCapturePrompt.java:334)
  at org.sikuli.util.OverlayCapturePrompt.paint(OverlayCapturePrompt.java:384)
  at javax.swing.RepaintManager$4.run(Unknown Source)
  … more
  [error] OverlayCapturePrompt: cropSelection: RasterFormatException

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1817556/+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 #678626]: Switching off all currently active highlighting

2019-02-27 Thread RaiMan
Question #678626 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/678626

RaiMan proposed the following answer:
Thanks for your systematic testing and feedback.

Of course I will add the color info to the logs - simply missed that.

-- 
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 #678739]: Status of bug #1817556 changed to 'Fix Committed' in Sikuli

2019-02-27 Thread RaiMan
Bug #1817556 status changed in Sikuli:

In Progress => Fix Committed

https://bugs.launchpad.net/sikuli/+bug/1817556
"[1.1.4] IDE: Toolbar buttons: crash if capture selection is drawn to another 
screen --- fixed 2019-02-26 build# 211"

This bug is linked to #678739.
IDE Offset Button
https://answers.launchpad.net/sikuli/+question/678739

-- 
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 1817853] [NEW] findAll Fail

2019-02-27 Thread Jeff_Vallis
Public bug reported:

1.1.3(2018-06-07_14:48)/Linux4.15.0-36-generic/Java8(64)1.8.0_191-b12
v_Image2 = Pattern(v_Image).similar(x1)
if exists(v_Image2,0.2) and v_test == 0:
v_Pos  = find(v_Image2)
hover(Location(v_Pos.x,v_Pos.y))
v_Result = list(findAll(v_Image2))

I added the find and hover to see if the find work - it did the error was on 
the findAll
I have an image and I am looping on x1 to check what similiarity matches and 
how many many matches = len(v_Result) 
[error] FindFailed ( 
/home/jeff/SikuliScripts_Linux/Subs/Vikings_Troops/Quantity Box.png: (4x11) 
seen at (221, 272) with 0.77 in S(0)[0,0 1366x768] E:Y, T:3.0 )

** 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/1817853

Title:
  findAll Fail

Status in Sikuli:
  New

Bug description:
  1.1.3(2018-06-07_14:48)/Linux4.15.0-36-generic/Java8(64)1.8.0_191-b12
  v_Image2 = Pattern(v_Image).similar(x1)
  if exists(v_Image2,0.2) and v_test == 0:
  v_Pos  = find(v_Image2)
  hover(Location(v_Pos.x,v_Pos.y))
  v_Result = list(findAll(v_Image2))

  I added the find and hover to see if the find work - it did the error was on 
the findAll
  I have an image and I am looping on x1 to check what similiarity matches and 
how many many matches = len(v_Result) 
  [error] FindFailed ( 
/home/jeff/SikuliScripts_Linux/Subs/Vikings_Troops/Quantity Box.png: (4x11) 
seen at (221, 272) with 0.77 in S(0)[0,0 1366x768] E:Y, T:3.0 )

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1817853/+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