sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

Thanks for the pointer.
I am really sorry about that stupid regression bug caused by the sloppy implementation of a new feature:

having a line like this

image1 =

and then pressing the capture button being in this line will name the
captured image as "image1.png" without asking and silently overwriting
an already existing "image1.png"

long story short: it is fixed with the nightly 2015-05-18+

... and again sorry for the inconvenience.

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

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

Title:
  [1.1.0] IDE hangup, recording an image to an array --- fixed
  2015-05-18+

Status in Sikuli:
  Fix Committed

Bug description:
  There is a small Python file with one line:

  btn_start=["btn_start1_1.png"]

  IDE is set to ask manual typing the image name.

  Trying to record the second screenshot in IDE:
  put a comma after the first image name:

  btn_start=["btn_start1_1.png", ]

  put the cursor after the comma, then click "Take screenshot", select
  again some region on the screen, e.g. Start button.

  Result: IDE hangs up, the dialog of image naming does not appear,
  killing is needed.

  Quite blocking for me, as I use many such arrays for alternative images search in flexible user interfaces.
  Earlier IDE versions did not hang up, at least 1.1.0 from 18.09.2014 which I used before for long time.

  both on Windows XP (Java SE RTE 1.7.0_60) and Win 7-64 (Java SE RTE 1.7.0_67-b01)
  Fresh version 1.1.0 2015-05-16

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1455812/+subscriptions