[1.0.1] Windows: 2 monitors: Capture button Modify Screen Bounds

Bug #1413796 reported by Steven Horita
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SikuliX
In Progress
High
RaiMan

Bug Description

Using SikuliIDE 1.1.0 (2015-01-16_01:00nightly) - python

I just recently installed this program on a Windows 7 Enterprise machine. I am using two monitors. I installed Sikuli onto a network drive.

When I first open the IDE, there are no problems, everything works the way that it should. Each time that I press one of the UI elements that adds code and takes a screenshot (for example: find, wait, click or rightClick) the screen bounds are changed by 2 pixels on all edges.

When I start, the screen bounds used to search are [0,0 1920x1080], then after adding a few elements, I run the code and get log messages like:

[log] DOUBLE CLICK on L(83,87)@S(0)[8,8 1904x1064]

The mouse events are still zero indexed though so in this case the mouse double clicked 8 pixels low and to the right of the intended target.

I looked to see if someone else had logged something like this but didn't see anything.

Thanks.

Revision history for this message
Steven Horita (sdhorita) wrote :
Revision history for this message
Steven Horita (sdhorita) wrote :

After trying a few more things, the change happens also when pressing the screenshot button.

Revision history for this message
RaiMan (raimund-hocke) wrote :

could you please start the IDE from a command line using the

runsikulix.cmd -d 3 c

and then just a
hover(<some_shot>)

and run it

and then send me the output you get on command line.

to make it easier:
runsikulix.cmd -d 3 c >log.txt

which would write the output directly into the file log.txt.

send the log data silently to my mail at https://launchpad.net/~raimund-hocke

summary: - UI Elements Modify Screen Bounds
+ [1.0.1] Windows: 2 monitors: Capture button Modify Screen Bounds
Changed in sikuli:
status: New → In Progress
importance: Undecided → High
assignee: nobody → RaiMan (raimund-hocke)
milestone: none → 1.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.