Re: [Inkscape-devel] PyXML missing - bug on 0.44pre1 on WinXP
On Wed, 31 May 2006, Bob Jamison wrote:
Exactly, which is why any last-minute fix must work perfectly. The
only absolutely safe way is to disable Effects. I would appreciate
any help on how to do this safely and effectively otherwise.
However, there might be a trick that people are ignoring.
If you look at the code in script.cpp, you can see that the "interpreter"
property of a .inx is processed thusly (here it is 'interpretstr'). We
are getting a value for "insertText ".
1. Say it is "python". It is looked up in the table, and given the
defaultval of "python"
2. The value for "python-interpreter" is looked up in the
"extension"
section of the prefs file.
3. If not found, and Win32, we try to search the PATH.
With a utility method in src/registrytool.cpp, we can get the path for
inkscape.exe, and
hardcode our python.exe's path into this method. However, look at 2.
We are not using that at all!
Wouldn't this be a safer fix for this release, to just make sure that Win32
guys
have their prefs set up to look for python? Just pre-can the entry.
If this doesn't seem to work out right, I will go ahead and use 3.
Could someone check this out, before I break anything?
Well, I can't really verify this, I do think putting this into script.cpp
so that it'll check the "locally installed" version before looking to the
system installed one is a good way to go. I suggested this earlier but
no one would tell me how to do that on Windows ;) It looks like this
would work for Perl and Ruby also, if we decide to ship those in the
future, is that true?
--Ted