More issues on Windows?
on Sun 3/27/2005 3:21 PM Ted Gould [ted@...10...]asked.
Are there more issues on Windows? Re: [Inkscape-user] "It also imports several formats like EPS" -howto on Windows
******************* Answer= YES
But first I would like to say thanks for the product, I think it will be very useful.
Using Inkscape-0.41-1.win32.exe(file mod dates Feb/8/2005) When I start Inkscape the extensions listed below fail to load.
BIGGEST ISSUE IS: Why does GIMP Gradients fail, when the dll is in the plugins folder? Also, if this plugin was working, can it use my existing gradients (if we give it a path), or is it for creating them? I tried dropping a .ggr file into the gradients folder but the editor did not find it.
When I create a gradient in the editor and save it, I can only use for that session. The next time I start up Inkscape and select gradient fill there are no existing ones to choose.
I believe the Extension scripts you refer to are the .inx files found in "C:\Program Files\Inkscape\share\extensions", is this correct?
Can these be edited for each user?
I tried to get the EPS ext to not fail. I edited (with notepad) the eps_input.inx file and put in "my path" to ghost script in place of the "path" but Inkscape complained and would not start. I put the file back to how it was originally but Inkscape still complained. When I put the backup copy of the file I had made, back into folder Inkscape started again. Is there a certain format the .inx must be saved as, like UTF-8 or something? OR does it check the file dates? I added my ghost script path to "Environment Variables" hoping this would make it find it. Still got error on EPS Input ext. I wonder if it has to do with gs actually being gswin32.exe?
All the extensions I can use are exe(windows) type, not compiled by me.
Extensions list: Extension failed to load because a dependency was not met: AI Input, AI Output, Dia Input, EPSI Output, EPS Input, GIMP Gradients, Grid, Postscript Input, Sketch Input, SVGZ Output, Text Input, Windows Metafile Input.
Craig
On Mon, 2005-03-28 at 12:08 -0600, Craig Gotthardt wrote:
BIGGEST ISSUE IS: Why does GIMP Gradients fail, when the dll is in the plugins folder? Also, if this plugin was working, can it use my existing gradients (if we give it a path), or is it for creating them? I tried dropping a .ggr file into the gradients folder but the editor did not find it.
Yes, it seems that this has always been a problem on Windows, but I was unaware of it. The loading of .dll's won't work until we have an exported API, which will be a little while. Until then, I'll be porting these over to internal extensions so they won't need to be loaded.
When I create a gradient in the editor and save it, I can only use for that session. The next time I start up Inkscape and select gradient fill there are no existing ones to choose.
Yes, gradients are stored in the document.
I believe the Extension scripts you refer to are the .inx files found in "C:\Program Files\Inkscape\share\extensions", is this correct?
Can these be edited for each user?
Not currently, but I don't think that is really a good idea. For the most part, the features that they will be dependent on will be system wide, like where ps2edit is found, not based on a per-user installation.
I tried to get the EPS ext to not fail. I edited (with notepad) the eps_input.inx file and put in "my path" to ghost script in place of the "path" but Inkscape complained and would not start. I put the file back to how it was originally but Inkscape still complained. When I put the backup copy of the file I had made, back into folder Inkscape started again. Is there a certain format the .inx must be saved as, like UTF-8 or something? OR does it check the file dates? I added my ghost script path to "Environment Variables" hoping this would make it find it. Still got error on EPS Input ext. I wonder if it has to do with gs actually being gswin32.exe?
All the extensions I can use are exe(windows) type, not compiled by me.
"path" just means to look in the path. Probably what you want to do is change the dependency to read "c:\blah\blah.exe" instead of putting in the XML. Any other Windows users here have Ghostscript using? I'm not sure how things work on Windows.
--Ted
On Mon, 2005-03-28 at 12:08 -0600, Craig Gotthardt wrote:
I tried to get the EPS ext to not fail. I edited (with notepad) the eps_input.inx file and put in "my path" to ghost script in place of the "path" but Inkscape complained and would not start. I put the file back to how it was originally but Inkscape still complained. When I put the backup copy of the file I had made, back into folder Inkscape started again. Is there a certain format the .inx must be saved as, like UTF-8 or something? OR does it check the file dates? I added my ghost script path to "Environment Variables" hoping this would make it find it. Still got error on EPS Input ext. I wonder if it has to do with gs actually being gswin32.exe?
All the extensions I can use are exe(windows) type, not compiled by me.
"path" just means to look in the path. Probably what you want to do is change the dependency to read "c:\blah\blah.exe" instead of putting in the XML. Any other Windows users here have Ghostscript using? I'm not sure how things work on Windows.
I tried briefly to monkey with that inx file too, on my Windows box. Do we need to do anything tricky to escape backslashes or anything? Also do you have a URL handy that breaks down what the various tags are in an inx file?
Alan
On Tue, 2005-03-29 at 06:27 -0500, R. Alan Monroe wrote:
I tried briefly to monkey with that inx file too, on my Windows box. Do we need to do anything tricky to escape backslashes or anything? Also do you have a URL handy that breaks down what the various tags are in an inx file?
There shouldn't be any magic like escaping, atleast not more than a normal XML file. (The same XML parser is used internally for the .inx files and .svg files). Unfortunately the format is pretty immature right now. The best documentation is here:
http://cvs.sourceforge.net/viewcvs.py/inkscape/inkscape/doc/extension_system...
--Ted
On Tue, 2005-03-29 at 06:27 -0500, R. Alan Monroe wrote:
I tried briefly to monkey with that inx file too, on my Windows box. Do we need to do anything tricky to escape backslashes or anything? Also do you have a URL handy that breaks down what the various tags are in an inx file?
There shouldn't be any magic like escaping, atleast not more than a normal XML file. (The same XML parser is used internally for the .inx files and .svg files). Unfortunately the format is pretty immature right now. The best documentation is here:
After a little investigation, I think this is a path problem of some kind.
My %PATH% was:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared;C:\Program Files\Common Files\Adaptec Shared\System;c:\python23;C:\Program Files\Executive Software\Diskeeper;C:\PROGRA~1\CHEZSC~1\csv6.9c\i3nt; C:\PROGRA~1\Tcl\bin
I tried two approaches to see what happened. First I opened a cmd prompt and tacked on my ghostscript path (c:\utils\gs\gs8.50\bin) to the %PATH% variable.
Later I tried adding the ghostscript bin folder in the system-wide environment variables under My Computer's properties.
In both cases I tracked what inkscape did at launch time with Sysinternals Filemon. It looked for gswin32.exe in every folder EXCEPT the newly-added ghostscript folder (It stops looking, after trying the last folder in the OLD path, the TCL bin folder). I can't explain WHY this happens, but it seems repeatable. I have not yet rebooted to see if that makes a difference. Will try that next.
804 8:59:48 PM inkscape.exe:3456 QUERY INFORMATION C:\WINDOWS\system32\gswin32.exe FILE NOT FOUND Attributes: Error 805 8:59:48 PM inkscape.exe:3456 OPEN C:\WINDOWS\system32\ SUCCESS Options: Open Directory Access: All 806 8:59:48 PM inkscape.exe:3456 DIRECTORY C:\WINDOWS\system32\ NO SUCH FILE FileBothDirectoryInformation: gswin32.exe 807 8:59:48 PM inkscape.exe:3456 CLOSE C:\WINDOWS\system32\ SUCCESS 808 8:59:48 PM inkscape.exe:3456 QUERY INFORMATION C:\WINDOWS\gswin32.exe FILE NOT FOUND Attributes: Error 809 8:59:48 PM inkscape.exe:3456 OPEN C:\WINDOWS\ SUCCESS Options: Open Directory Access: All 810 8:59:48 PM inkscape.exe:3456 DIRECTORY C:\WINDOWS\ NO SUCH FILE FileBothDirectoryInformation: gswin32.exe 811 8:59:48 PM inkscape.exe:3456 CLOSE C:\WINDOWS\ SUCCESS 812 8:59:48 PM inkscape.exe:3456 QUERY INFORMATION C:\WINDOWS\System32\Wbem\gswin32.exe FILE NOT FOUND Attributes: Error 813 8:59:48 PM inkscape.exe:3456 OPEN C:\WINDOWS\System32\Wbem\ SUCCESS Options: Open Directory Access: All 814 8:59:48 PM inkscape.exe:3456 DIRECTORY C:\WINDOWS\System32\Wbem\ NO SUCH FILE FileBothDirectoryInformation: gswin32.exe 815 8:59:48 PM inkscape.exe:3456 CLOSE C:\WINDOWS\System32\Wbem\ SUCCESS 816 8:59:48 PM inkscape.exe:3456 QUERY INFORMATION C:\Program Files\Common Files\Roxio Shared\DLLShared\gswin32.exe FILE NOT FOUND Attributes: Error 817 8:59:48 PM inkscape.exe:3456 OPEN C:\Program Files\Common Files\Roxio Shared\DLLShared\ SUCCESS Options: Open Directory Access: All 818 8:59:48 PM inkscape.exe:3456 DIRECTORY C:\Program Files\Common Files\Roxio Shared\DLLShared\ NO SUCH FILE FileBothDirectoryInformation: gswin32.exe 819 8:59:48 PM inkscape.exe:3456 CLOSE C:\Program Files\Common Files\Roxio Shared\DLLShared\ SUCCESS 820 8:59:48 PM inkscape.exe:3456 QUERY INFORMATION C:\Program Files\Common Files\Adaptec Shared\System\gswin32.exe FILE NOT FOUND Attributes: Error 821 8:59:48 PM inkscape.exe:3456 OPEN C:\Program Files\Common Files\Adaptec Shared\System\ SUCCESS Options: Open Directory Access: All 822 8:59:48 PM inkscape.exe:3456 DIRECTORY C:\Program Files\Common Files\Adaptec Shared\System\ NO SUCH FILE FileBothDirectoryInformation: gswin32.exe 823 8:59:48 PM inkscape.exe:3456 CLOSE C:\Program Files\Common Files\Adaptec Shared\System\ SUCCESS 824 8:59:48 PM inkscape.exe:3456 QUERY INFORMATION C:\python23\gswin32.exe FILE NOT FOUND Attributes: Error 825 8:59:48 PM inkscape.exe:3456 OPEN C:\python23\ SUCCESS Options: Open Directory Access: All 826 8:59:48 PM inkscape.exe:3456 DIRECTORY C:\python23\ NO SUCH FILE FileBothDirectoryInformation: gswin32.exe 827 8:59:48 PM inkscape.exe:3456 CLOSE C:\python23\ SUCCESS 828 8:59:48 PM inkscape.exe:3456 QUERY INFORMATION C:\Program Files\Executive Software\Diskeeper\gswin32.exe FILE NOT FOUND Attributes: Error 829 8:59:48 PM inkscape.exe:3456 OPEN C:\Program Files\Executive Software\Diskeeper\ SUCCESS Options: Open Directory Access: All 830 8:59:48 PM inkscape.exe:3456 DIRECTORY C:\Program Files\Executive Software\Diskeeper\ NO SUCH FILE FileBothDirectoryInformation: gswin32.exe 831 8:59:48 PM inkscape.exe:3456 CLOSE C:\Program Files\Executive Software\Diskeeper\ SUCCESS 832 8:59:48 PM inkscape.exe:3456 QUERY INFORMATION C:\PROGRA~1\CHEZSC~1\csv6.9c\i3nt\gswin32.exe FILE NOT FOUND Attributes: Error 833 8:59:48 PM inkscape.exe:3456 OPEN C:\PROGRA~1\CHEZSC~1\csv6.9c\i3nt\ SUCCESS Options: Open Directory Access: All 834 8:59:48 PM inkscape.exe:3456 DIRECTORY C:\PROGRA~1\CHEZSC~1\csv6.9c\i3nt\ NO SUCH FILE FileBothDirectoryInformation: gswin32.exe 835 8:59:48 PM inkscape.exe:3456 CLOSE C:\PROGRA~1\CHEZSC~1\csv6.9c\i3nt\ SUCCESS 836 8:59:48 PM inkscape.exe:3456 QUERY INFORMATION C:\PROGRA~1\Tcl\bin\gswin32.exe FILE NOT FOUND Attributes: Error 837 8:59:48 PM inkscape.exe:3456 OPEN C:\PROGRA~1\Tcl\bin\ SUCCESS Options: Open Directory Access: All 838 8:59:48 PM inkscape.exe:3456 DIRECTORY C:\PROGRA~1\Tcl\bin\ NO SUCH FILE FileBothDirectoryInformation: gswin32.exe 839 8:59:48 PM inkscape.exe:3456 CLOSE C:\PROGRA~1\Tcl\bin\ SUCCESS 840 8:59:48 PM inkscape.exe:3456 WRITE C:\Documents and Settings\amonroe\Application Data\Inkscape\extension-errors.log SUCCESS Offset: 704 Length: 72
After a little investigation, I think this is a path problem of some kind.
I tried two approaches to see what happened. First I opened a cmd prompt and tacked on my ghostscript path (c:\utils\gs\gs8.50\bin) to the %PATH% variable.
Later I tried adding the ghostscript bin folder in the system-wide environment variables under My Computer's properties.
I went on to try making the path really short. I cut it down to c:\windows\system;c:\windows;c:\utils\gs\gs8.50\bin Filemon still showed it never even attempted to read the ghostscript folder.
I tried adding a trailing slash to the folder name, no effect.
Finally I changed the order so that the ghostscript folder was in the middle of the path rather than the end, result SUCCESS. No more errors about EPS Input in extension-errors.log.
Can anyone explain this? Maybe a fluke with the compiler used and how it reads environment variables?
The plugin still doesn't WORK, but we're getting closer, anyway. I can see with filemon that it reads the .eps file I pick in the import dialog, but Process Explorer doesn't show gswin32, or any other child process, being spawned from the inkscape process.
I've attached my modified eps_input.inx too in case it matters.
Alan
participants (3)
-
Craig Gotthardt -
R. Alan Monroe -
Ted Gould