sikuli-driver team mailing list archive

[dinev <1529457@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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

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

Title:
  Auto generated images names causes a problem

Status in Sikuli:
  New

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