Sweet, it looks like PyXML is all that was missing... and it was specifically your extensions that were giving that error. Ted's don't error, and they also don't seem to work for me on win32 though either. Yours work great now! Thanks much!
Also, it's probably a question for Ted, but why does it open a new window to apply the extension?
-Josh
PS: Thanks for making extension work on win32 Ted!!
-----Original Message----- From: aaron@...749... [mailto:aaron@...749...] Sent: Wednesday, May 11, 2005 1:03 PM To: Joshua A. Andler; Inkscape Devel List Subject: Re: [Inkscape-devel] Effects on Windows
Joshua A. Andler wrote:
Nevermind that... it was on old prefs file in an old location... got
the
menu to show up, but no extensions seem to work for me...
I get the following in the log window when I try to use them:
** (inkscape.exe:2064): CRITICAL **: file extension/implementation/script.cpp: line 630 (virtual void
Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension:
:Effect*, SPView*)): assertion `mydoc != NULL' failed
Perl and/or Python (depending on the effect) need to be installed and
in
the path. And then each effect will have its own requirements. Dropshadow requires Perl and XML::XQL::DOM. My effects require Python and PyXML from http://pyxml.sourceforge.net/.
Which effect were you trying?
There definately needs to be a way for the user to know what part of
the
equation is missing. A less that perfect but functional way of doing this would be to display stderr from effects to the user. But output from scripts like this is hidden from windows users even if they start form the console. (I think.)
Aaron Spike