This may be an odd suggestion but having an error console embedded in the GUI would be an enabled preference - essentially these are written to the command line (and therefore mostly lost to be insignificant) - but having a debugging window is what you are suggesting. It can capture and report the state of the program as well as protect against failures that would cause loss of work which (if designed intentionally could be dumped as a save prior to any critical check that may cause an application crash) to be saved before failure. Is that what you mean? =)
-N
Sent from my iPhone
On Jun 7, 2020, at 11:15 AM, wiesi@posteo.net wrote:
Hello everyone,
is there a possibility to get some error status and/or error messages when executing actions via, e.g., activate_action()? I had a look at the glibmm documentation but couldn't find anything regarding this topic.
I've just included executing Inkscape actions from the internal Python interpreter feature I'm porting to the current master branch (https://gitlab.com/wiesi/inkscape/-/tree/python-internal-1) and it would be nice (maybe even mandatory) for the Python user to get some feedback whether an action was successful and a meaningful error message if not.
Can anyone point me in the right direction? Does glibmm have some infrastructure for this task that I'm just unable to find or does it really require some extended surgery?
Thanks, Thomas
Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org