[check] IDE: Auto generated image names using image = should not overwrite.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
In Progress
|
Medium
|
RaiMan |
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.
Happy holidays
Neven
description: | updated |
summary: |
- Auto generated images names causes a problem + [request] IDE: Auto generated image names using image = should not + overwrite. |
Changed in sikuli: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → RaiMan (raimund-hocke) |
milestone: | none → 2.0.0 |
Changed in sikuli: | |
milestone: | 2.0.0 → 2.0.1 |
summary: |
- [request] IDE: Auto generated image names using image = should not + [check] IDE: Auto generated image names using image = should not overwrite. |
I will revise this feature in version 2.0 to have more options.
I plan to support image groups, where a group is represented by an image folder.
And the support for capturing images and organize them will be a separate app, so it can be used for all situations including the IDE.
But for now you have to live with that "by design" effect:
If you want to use this feature, you have to follow your own naming convention, to assure, that your images are not messed up.
in your case:
class screenDialog1: g1_button_ OK = "button_OK.png" g2_button_ OK =
screenDialo
class screenDialog2:
screenDialo