Has anyone tried to use effects on Win32. I tried it at work today and failed. When I try to run a script I get:
** (inkscape.exe:2648): CRITICAL **: file extension/implementation/script.cpp: line 586 (virtual void Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, SPView*)): assertion 'mydoc != NULL' failed
I'm having great difficulty diagnosing whether it fails before or after running the script. Is it supposed to work?
Aaron Spike
On Mon, 2005-04-11 at 15:42 -0500, aaron@...749... wrote:
Has anyone tried to use effects on Win32. I tried it at work today and failed. When I try to run a script I get:
** (inkscape.exe:2648): CRITICAL **: file extension/implementation/script.cpp: line 586 (virtual void Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, SPView*)): assertion 'mydoc != NULL' failed
I'm having great difficulty diagnosing whether it fails before or after running the script. Is it supposed to work?
Well, they should. All of the pipe stuff has been patched to work, but I think that some of the scripts have hard coded paths to things like the perl binary that breaks many of them. Also, some of the dependencies fail more often for a reason unknown to me :( I'd love to see them work -- I'd hate for Windows users to miss out on the fun :)
--Ted
Ted Gould wrote:
On Mon, 2005-04-11 at 15:42 -0500, aaron@...749... wrote:
Has anyone tried to use effects on Win32. I tried it at work today and failed. <snip> I'm having great difficulty diagnosing whether it fails before or after running the script. Is it supposed to work?
Well, they should. All of the pipe stuff has been patched to work, but I think that some of the scripts have hard coded paths to things like the perl binary that breaks many of them. Also, some of the dependencies fail more often for a reason unknown to me :( I'd love to see them work -- I'd hate for Windows users to miss out on the fun :)
I'm a both user because of work. If it is supposed to work, I'd love to help get the kinks worked out. I seem to have a lot more trouble getting useful feedback on Windows. Do you have any clue as to what (or how) I should test next? I see the message whenever I click on an effect that is supposed to call an external script. So far I haven't been able to fashion a script to get any feedback about the interaction at all. I will keep trying.
Aaron Spike
Ok. I spent a little more time on this. In script.inx file, this works on Linux:
<command reldir="extensions">script.py</command>
And this works on Windows:
<command reldir="path">python "C:\Path\To\Script\script.py"</command>
What is the proper syntax for a write once run anywhere *.inx file?
Aaron Spike
On Tue, 12 Apr 2005 aaron@...749... wrote:
Ok. I spent a little more time on this. In script.inx file, this works on Linux:
<command reldir="extensions">script.py</command>
And this works on Windows:
<command reldir="path">python "C:\Path\To\Script\script.py"</command>
What is the proper syntax for a write once run anywhere *.inx file?
Well, I think that the problem is that we don't have one. I'm open to suggestions. Does that mean that Windows won't execute the #! at the top of files?
--Ted
ted@...11... wrote:
On Tue, 12 Apr 2005 aaron@...749... wrote:
Ok. I spent a little more time on this. In script.inx file, this works on Linux:
<command reldir="extensions">script.py</command>
And this works on Windows:
<command reldir="path">python "C:\Path\To\Script\script.py"</command>
What is the proper syntax for a write once run anywhere *.inx file?
Well, I think that the problem is that we don't have one. I'm open to suggestions. Does that mean that Windows won't execute the #! at the top of files?
Windows uses an association between file extension and applications that is stored in the registry.
I have a bunch of random thoughts/questions: -with option one can Inkscape be taught to call the script in such a way that windows can choose the interpreter properly (and function with pipes? -what other platforms will have special nuances that need to be delt with? -with option two could the inkscape extensions directories be added to a search path environment variable (like java classpath) that is used by the interpreter to avoid absolute paths? -Could inkscape be given a more flexible way to construct the command line? eg. <interpreter reldir="path">python</interpreter> <scriptfile reldir="extensions">script.py</scriptfile> would yeild 'python "path to script/script.py" params...
Aaron Spike
ted@...11... wrote:
On Tue, 12 Apr 2005 aaron@...749... wrote:
Ok. I spent a little more time on this. In script.inx file, this works on Linux:
<command reldir="extensions">script.py</command>
And this works on Windows:
<command reldir="path">python "C:\Path\To\Script\script.py"</command>
What is the proper syntax for a write once run anywhere *.inx file?
Well, I think that the problem is that we don't have one. I'm open to suggestions. Does that mean that Windows won't execute the #! at the top of files?
--Ted
Maybe it could be specified in the file URI-style, then converted at runtime to whatever the platform wants. like file://c/Path/To/Script/script.py and to avoid absolute names, maybe consider the .inx file to be the Document Base and consider the path to be relative to that.
Bob
participants (3)
-
unknown＠example.com -
Bob Jamison -
Ted Gould