sikuli-driver team mailing list archive

[Greg Howell <question245030@xxxxxxxxxxxxxxxxxxxxx>]

Question #245030 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/245030

    Status: Needs information => Open

Greg Howell gave more information on the question:
I have some more interesting things to point out from my investigation.  To give you an idea of my setup, I have a Dell laptop on a docking station and to the right of it I have a Samsung BX2440 monitor which is set as my primary display.  I thought maybe it was the issue with the laptop being one of the displays, so I borrowed a monitor from another computer (a Dell something square screen) and made it the second display, closing the laptop lid.  The samsung is plugged into monitor 1 and the Dell into monitor 2 on the docking station.  At first I kept the samsung as the primary and tried the program.  Again it sees the samsung as both screen(0) and screen(1) and behaved as before.  But when I made the dell the primary display I got some weird results.  The red highlight for screen(0) started on the far right edge of the Dell monitor and extended halfway across the samsung.  The red highlight for screen(1) was around the whole screen of the Dell monitor, but it had shifted the left 3/4 of the screen up about the height of the start bar at the bottom.  And then when my program did the selectRegion on screen(1) it only allowed me to select on the Samsung and what was weird is that it had shifted the contents of the Samsung screen over to the right about 2/3 of the screen so the left 2/3 was black and the right 1/3 showed 1/3 of the contents of the display.  It said "Please select the region" in the black part but only allows me to actually select something over in the right 1/3 of the screen.  And then the program crashes on the observe statement because it says 
[error] Region(2560,225,639,358) outside any screen - subsequent actions might not work as expected
[error] Region(2560,225,639,358) outside any screen - subsequent actions might not work as expected
[error] script [ *Untitled ] stopped with error in line 18
[error] java.lang.NullPointerException ( java.lang.NullPointerException )

Could it be a display driver interaction thing?  My display driver is an
NVIDIA Quadro K2100M.

ok, just got your other response and I ran from the command line with
debug like you mentioned.  It tells me this:

[debug] Screen: initScreens: basic initialization (2 Screen(s) found)
[debug] *** monitor configuration (primary: 0) ***
[debug] Screen 0: S(0)[0,0 1280x1024]
[debug] Screen 1: S(1)[1280,-56 1920x1080]
[debug] *** end monitor configuration ***

That was with the two physical monitor configuration (no laptop screen) and the Dell as the primary display.  So I noticed the negative Y position on screen(1).  So I went back into my screen config and made the tops of the monitors line up.  Now it shows:
[debug] Screen 0: S(0)[0,0 1280x1024]
[debug] Screen 1: S(1)[1280,0 1920x1080]

And everything works beautifully as expected!!!  I think that was the
culprit.  It doesn't handle the negative coordinates well at least for
Y.  I then tried flipping the monitors again, making the one on the
right the primary (the samsung 1920x1080) and the Dell the secondary.
That made screen(1)s position -1280,0 but it all still behaved exactly
as expected.  I think it just doesn't like a negative Y value.  What do
you think?

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.