sikuli-driver team mailing list archive

[shawn kirsch <shawn.kirsch@xxxxxxxxxxxxxxxx>]

What I mean to say is that if an image fail lookup occurs in another
script it doesn't tell you where basically...it tells you the image it's
failing on, but ideally it would say what line the fail occurs on.  i
mean i can ctrl + f  and find it, but...

** Attachment added: "sikuli_findfail.png"
   https://bugs.launchpad.net/sikuli/+bug/1230928/+attachment/3846022/+files/sikuli_findfail.png

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

Title:
  Error Tracebacks Display Wrong Line

Status in Sikuli:
  New

Bug description:
  If I have a lib called testLib and I import it into another moduel say
  curModule and then call a function in testLib, if it fails in the
  function I'm calling to testLib it will say there was an error in
  curModule on line whatever, although it's actually failing on a
  separate line in the testLib.  Can sikuli not inspect it deep enough?
  this make debugging a pain in the ass.

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