OK, thanks for clarification and example.
This is a bug. I will check and fix as soon as possible.
** Summary changed:
- Error Tracebacks Display Wrong Line
+ Error Tracebacks Display Wrong Line when FindFailed in imported script
** Summary changed:
- Error Tracebacks Display Wrong Line when FindFailed in imported script
+ [1.0.1] Error Traceback Display Wrong Line when FindFailed in imported script
** Changed in: sikuli
Status: New => Fix Committed
** Changed in: sikuli
Importance: Undecided => High
** Changed in: sikuli
Assignee: (unassigned) => RaiMan (raimund-hocke)
** Changed in: sikuli
Milestone: None => 1.1.0
--
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:
[1.0.1] Error Traceback Display Wrong Line when FindFailed in imported
script
Status in Sikuli:
Fix Committed
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
_______________________________________________
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
