On Fri, May 29, 2009 at 10:11 AM, Ulf Erikson <ulferikson@...400...> wrote:
I would suggest following the other examples. Making the main application a console application seems to stop Windows from spawning new consoles for subprocesses.
But instead it makes Inkscape itself spawn a console window for itself, which is worse.
Last time I looked into it, if an extension launched from Inkscape-mwindows opens a console, you just need to make sure it has pythonw listed as interpreter in its .inx file. That fixed it for my custom extension on Windows, but it's not a portable fix, as there's no pythonw on other systems. The file src/extension/implementation/script.cpp has code which is supposed to replace python to pythonw automatically on Windows, but it looks like it does not work for some reason - if someone could investigate that it would be great.