sikuli-driver team mailing list archive

[surfdork <715364@xxxxxxxxxxxxxxxxxx>]

Yes, I'm on 0.10.
Has this issue been reported in the past?
Why I'm asking is to find a less intrusive fix than completly restoring a machine.  What persistent state can cause this kind of behavior?  Are there files I can delete or other applications to uninstall instead of restoring a machine?
I plan on trying the latest version after extensive testing.
Will the new version import subprocess?

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

Title:
  Object found with cursor yet click fails on the identified object

Status in Sikuli:
  New

Bug description:
  Sometimes Sikuli finds an object yet fails to click on it. The cause
  is unknown, I have no clear repro steps.

  A user will execute a Sikuli script either via the Sikuli IDE or from the NetBeans IDE.
  The cursor will position itself over the object to interact with yet the click will fail.
  When in this state a user can create a specifc script to click or double click on any other object.  The script will fail with the cursor visually finding the object.
  Object color change does not ioccur indicating the click action was not executed.
  I am not sure how to get out of the state, close and reopen Sikuli does not fix the issue, uninstall/reinstall does not fix the issue I've had to reimage multiple (am reimaging a test machine now).

  
  This is what's returned in Sikuli IDE
  [sikuli] double click on (1747,1179), MOD: 0
  [sikuli] showTarget 1722 1154 50 50

  What other information can be provided?

  Where else can I look for pertinent log files to diagnose this issue?