|
Post by thadude on Apr 20, 2019 5:50:08 GMT
I experienced a problem with my script where it suddenly stopped. The dialog said user abort. However I did not stop my script.
I don't believe my script clicked the stop button. If it did its a bug because I set the click location to 500,500 and I have the button off to the side of the screen around 0,300.
What are the causes for "user abort" dialog. Is there any logging to help troubleshoot this?
thanks
|
|
|
Post by AnkuLua on Apr 20, 2019 12:16:14 GMT
For Pro2 users, you can hide the stop button and use volume down to stop the script.
|
|
|
Post by thadude on Apr 20, 2019 20:47:18 GMT
Thanks, but would you be able to list the expected cases when "user abort" occurs?
|
|
|
Post by AnkuLua on Apr 20, 2019 23:36:17 GMT
Thanks, but would you be able to list the expected cases when "user abort" occurs? The only case for "user abort" is stop button clicked, either by man or script.
|
|
|
Post by Exilereven on Apr 21, 2019 1:44:39 GMT
If your button is "out of the way" then my guess qoukd be that you are stopping the script somewhere it shouldnt. Try placing a tag near your scriptExit() like this
print('scriptExit()')
And label them so you can tell which, where, when its firing if it is. But it def sounds like you have a break from a loop somewhere that leads to a scriptExit() that you werent expecting.
|
|
|
Post by thadude on Apr 22, 2019 3:33:40 GMT
Thank you both. I don't have any scriptExits() but the problem has since went away so not sure what it was.
|
|