Alvin Penner wrote:

the Adib wrote:

...

Any reason why there is a need for a separate application?

to the best of my knowledge, there is no other way of trapping error messages to the console in Windows. One can, of course, run the Python script by the same author (at http://kaioa.com/node/42), but this is not really suitable for 'most' users.

What I've done is that I've modified my build.xml to output a console application instead of a GUI application. This hardly ever leads to conflicts (as these switches are usually left alone). I just have to make sure I don't commit my version of build.xml, but this is not a big problem.

Of course this is only interesting for developers, and I do think it makes sense to make the console messages more accessible in Inkscape, but perhaps just adding inkscapec.exe to Inkscape's directory would not be accessible enough. Perhaps a separate shortcut that would start inkscapec?

Yann Papouin wrote:

inkscape.exe can be used in command line, for a .bat file for example ?

Yes, but that's not what this discussion was about (and you don't even have to compile it as a console application for that). The problem is that Inkscape prints debug messages to stdout. On Linux you can easily see these by starting Inkscape from a shell, but on Windows you won't see them, even if you start Inkscape from the commandline. This prevents most Windows users from using this potentially valuable debugging resource.

There are two things you can do to remedy the situation. One is to compile Inkscape as a console application. This doesn't change it's behaviour at all, except that Windows does attach a console to its stdout. The other is to run it through inkscapec.exe. The latter is much easier for non-developers.

I'm not sure of that and tested with 0.46, I'm not able to do the same thing because the command line is not working (Win32)

my bat file /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// @echo "PNG rendering" "C:\program files\inkscape\inkscape.exe" -f mypicture.svg -d 90 -e mypicture.png Pause ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

output with inkscape.exe:

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// "PNG rendering"

C:\Documents and Settings\yanapa\Mes documents\temp\DEC_Yann>"C:\program files\inkscape\inkscape.exe" -f mypicture.svg -d 90 -e mypicture.png

C:\Documents and Settings\yanapa\Mes documents\temp\DEC_Yann>Pause Appuyez sur une touche pour continuer... ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

output with inkscapec.exe:

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// "PNG rendering"

C:\Documents and Settings\yanapa\Mes documents\temp\DEC_Yann>"C:\program files\inkscape\inkscapec.exe" -f mypicture.svg -d 90 -e mypicture. png DPI: 90 Background RRGGBBAA: ffffff00 Area 0:0:195:120 exported to 195 x 120 pixels (90 dpi) Bitmap saved as: mypicture.png

C:\Documents and Settings\yanapa\Mes documents\temp\DEC_Yann>Pause Appuyez sur une touche pour continuer... ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

2009/5/26 Jasper van de Gronde <th.v.d.gronde@...528...>

Yes, but that's not what this discussion was about (and you don't even have to compile it as a console application for that)

Yes you're right, I knew for the "no output" thing but not for need for full path. Thank you.

2009/5/27 bulia byak <buliabyak@...400...>

On Wed, May 27, 2009 at 4:19 AM, Yann Papouin <yann.papouin@...400...> wrote:

...

I'm not sure of that and tested with 0.46, I'm not able to do the same

thing

...

because the command line is not working (Win32)

actually it should output the file, just give no output:

http://wiki.inkscape.org/wiki/index.php/Inkscape_Wiki:FAQ#I.27m_on_Windows.2...

-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

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.