sikuli-driver team mailing list archive

[Caio Araújo Teixeira Campos <802690@xxxxxxxxxxxxxxxxxx>]

Thanks for your quick responses.

Answers preceded by A:

--- you say: It still doesn't work.

does this mean using
java -jar path-to-sikuli-script.jar path-to-your-script.sikuli ???

A: yes

--- the test
The screen size is 1024x768, but the mouse does not reach the lower right corner: (1023,767).
The captured upper right 300x300 is found with no problem.

A: Doesn't the screen start on 0,0? I thought it was right the mouse
reaching 1023,767

--- you say:
Running this way I don't know if the menu is black or if it is not black and Sikuli can't find it.

pls. clarify what you mean, I do not understand.

A: When using Sikuli to screen capture or matching preview I'm certain
that Sikuli sees black regions, but using the jar, instead of the IDE,
there is no way to know if Sikuli is seeing things black.

--- real life
it would be helpful, to have a screenshot of the scene and the relevant part of the script.
put all together in a zip and attach.

A: To see the problem happening you don't even need a script, just try
to take a screenshot and you will see the black thing. I will try to get
a screenshot of the scene but I don't have it now since the application
I'm testing is confidential and I couldn't find a similar bug yet.

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/802690

Title:
  Part of a dialog gets black when trying to take a screenshot, run
  sikuli script or use Matching Preview

Status in Sikuli:
  New

Bug description:
  When I try  to take a screenshot, run sikuli script or use Matching
  Preview in a specific dialog, part of this dialog gets black.

  If I move the dialog this won't happen anymore, so I can still run my
  script just dragging and dropping my dialog before performing my
  actions on this dialog.

  It is the first time I see it and it only happens with this dialog.

  I'm running Sikuli X-1.0rc2 x86_64, on a Red Hat Enterprise Linux
  Server release 6.1 (Santiago) through a VNC session. (Sikuli
  installation and my VNC server are on this machine)

  I'm not sure how to reproduce this bug since it is the only situation
  that I can see this happening.

  I've already tried in a new VNC session but the same problem happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/802690/+subscriptions