Question #256439 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/256439
RaiMan proposed the following answer: Again, to make it clear for version 1.1.0+: The error place even deep down in a module structure is exactly shown if the error/exception is produced on the Python level (one of the defined Python exceptions) Only if the exception is caused in the Java code beneath (might be some bug in the SikuliX Java API), you only get the top level position in the main module of the stack trace. So in this case you should check, wether the returned App object is not- None, before using it like appObject.function(). -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
