I often write effects in Python that raise an exception, and therefore send no output to STDOUT. Inkscape responds with:
Extension::Script: Unknown error for pclose : Success /tmp/ink_ext_qL04b1:1: parser error : Document is empty
^ /tmp/ink_ext_qL04b1:1: parser error : Start tag expected, '<' not found
^
** (inkscape:6769): CRITICAL **: virtual void Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, SPView*): assertion `mydoc != NULL' failed
Is that just a healthy warning? I also notice on occasion (though I can not reproduce it on command yet) that I experience a crash soon afterward.
So my question: Could stderr generated by scripts be captured into a gui window? This is of course unnecessary because, I can always run inkscape from the command line for debugging. But I thought the information might help users track down dependencies.
Aaron Spike
On Thu, 7 Apr 2005 aaron@...749... wrote:
Is that just a healthy warning? I also notice on occasion (though I can not reproduce it on command yet) that I experience a crash soon afterward.
Fixed on my machine :)
So my question: Could stderr generated by scripts be captured into a gui window? This is of course unnecessary because, I can always run inkscape from the command line for debugging. But I thought the information might help users track down dependencies.
Sounds like a good idea. Put it in as an RFE and e-mail me the number. I don't know that I'll get to it short term, but I think it is a good way to give feedback. (Though, dependencies should be caught earlier -- but feedback on other errors that could occur)
--Ted
ted@...11... wrote:
On Thu, 7 Apr 2005 aaron@...749... wrote:
Is that just a healthy warning? I also notice on occasion (though I can not reproduce it on command yet) that I experience a crash soon afterward.
Fixed on my machine :)
So my question: Could stderr generated by scripts be captured into a gui window? This is of course unnecessary because, I can always run inkscape from the command line for debugging. But I thought the information might help users track down dependencies.
Sounds like a good idea. Put it in as an RFE and e-mail me the number. I don't know that I'll get to it short term, but I think it is a good way to give feedback. (Though, dependencies should be caught earlier -- but feedback on other errors that could occur)
REF #1178941 http://sourceforge.net/tracker/index.php?func=detail&aid=1178941&gro...
Aaron Spike
participants (1)
-
unknown＠example.com