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