@Rainer could you run a snippet, that produces the problem using DebugLevel 3 and send the log silently to my mail at https://launchpad.net/~raimund-hocke
either use -d 3 -c on command line or inline in code Debug.setDebugLevel(3) thanks ** Summary changed: - Linux System Always Uses Screen(0) + [1.1.0-Beta1] Linux System Always Uses Screen(0) -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/793723 Title: [1.1.0-Beta1] Linux System Always Uses Screen(0) Status in Sikuli: In Progress Bug description: I am using Sikuli version 1.0rc3 compiled from source on a Redhat EL4 system. I have a 3 monitor setup running X11R7.1.1 and it appears that Sikuli maps all operations to screen 0 i.e. DISPLAY :0.0. The getNumberScreens() method returns 3 as expected, and instantiating screen objects for Screen(0), Screen(1), and Screen(2) appear to work. Trying to use the screen objects to invoke click(), find(), etc. always result in an operation on screen(0) only. If I print the screen objects all 3 return the following: Screen(0)[0,0 1920x1200] E:Y, T:3.0 So, does this version of Sikuli support a multi-monitor Linux setup and if yes, what could I be doing wrong? Thanks... To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/793723/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
