jobenayoun
commented
11 years ago Hey Enrique, three things here you must take care:
- the namespace in which your exception may occur is here the local namespace of your function-slot (python only evaluates and build the namespace of such function when called and not parsed, only syntax errors are relevant when parsing is done)
- Qt catches by default all exceptions to avoid the main GUI thread to close in an unpredictable way and be sure all resources are correctly freed (Qt is not developed in python).
- when developing with python, it's good practice to embrace the python's official philosophy, that it's preferable to control the flow using exceptions and drive your code as such. Also, in a production context, I would say, it's quite required that you should have a solid exception handling presence in your code.
This is not related to the plugin but just is common pitfalls you get used to when experienced with python and Qt. hope that help, cheers. -- jon
Enrique-Caballero
Hey Steven, I have been using your plugin for a long time now, almost since the beginning, and I've always had this problem but always assumed that it was due to user error. I have now done a lot of testing and believe that it is not user error. Here it is.
Not all errors will log to the Softimage Script Editor, actually most of them will not.
If there is an error that halts the creation of the PYQT window then it will log that and fail the creation, but if the error is part of a function call that is connected to a button, no error will log.
For example, please go to the pyqt_example.py and edit line 40. Application.LogMessage( self.lineedit.text() )
and add a + 1 to it, to create a Concatanation error. so the line reads like this
Application.LogMessage( self.lineedit.text() + 1)
so this should give us a concatenate error when the button is pressed.
save the script and reload the plugin, reload the window and press the "Log Text" Button. No error will be spit out of the script editor, and the button will simply do nothing.
This problem happens with ANY script problem that is called as a function by a button in the UI. And makes troubleshooting complicated menu's and actions very difficult.
The way I deal with it now is that everytime a function is called by a button, I do a TRY and EXCEPT where it catches ALL exceptions, and then logs then force it to log a message. This helps me diagnose, but it does not help me find the line number with the error.
Anyway if you could please look into this that would be awesome, I love your plugin and rely on it quite heavily