There is this nasty behaviour if I call Inkscape from an different directory than where the inkscape.exe is then Inkscape does not find all the share/ etc. directories.
Inkscape does not need to simply use the current worked directory but the directory where Inkscape.exe is. If that is possible.
Adib. -- Am Sonntag, den 01.07.2007, 07:41 -0500 schrieb Aaron Spike:
Bob Jamison wrote:
We do not find Python.exe via PATH. What Inkscape does is to add /python to the application_path at startup. This is done via code that writes to the Registry at startup. /python and /perl are added to the application_path this way. This preempts PATH and basically has nothing to do with it.
I remembered reading something like that in the code. Thanks for the explanation.
Also, the CurrentDirectory() on win32 is set to the directory where inkscape.exe is.
There are a few apparent bugs that result from this. Would it be possible to make the CurrentDirectory() the user's My Document folder when run from the gui, and set it to the current folder when envoked from the command line. Now that might not fix the problems with invocations inside of scripts unless they inherit My Documents from the environment of the gui process. If this is possible I think it might fix a few of the things that I've heard users complain were odd in the chatroom.
Aaron Spike
This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel