Better notification of PythonScript error

Got a good idea? You can suggest new features here.
Post Reply

Add better identification of erroring PythonScript

Leave it the way it is.
0
No votes
Prompt to open the script.
0
No votes
Just open the script.
0
No votes
Prompt to open script and mark the line that has the fault.
5
100%
Just open the script and mark the line that has the fault.
0
No votes
I have not a clue what you are mumbling about.
0
No votes
 
Total votes: 5

User avatar
kgschlosser
Site Admin
Posts: 3402
Joined: Fri Jun 05, 2015 5:43 am
Location: Rocky Mountains, Colorado USA

Better notification of PythonScript error

Post by kgschlosser » Tue May 09, 2017 6:56 pm

in EG 0.5-rc2 there was a fix that was put into place. it corrected an issue where you would get a very illusive error message saying "NoneType object has no attribute PrintError". That has been fixed. But I know there are quite a few folks out there with more then one or 2 PythonScripts so trying to locate the one that has the error can be very daunting. So I had EG select the actual script that has the error. I am thinking this may not be enough for the newer users of EG. and I would like to put it to a vote on possibly adding better identification of the erroring script.
If you like the work I have been doing then feel free to Image

Post Reply