[Bf-committers] Fixing Windows console
dfelinto at gmail.com
Sun Apr 7 01:22:38 CEST 2013
"The problem with this approach is that calling Blender.exe from cmd
What do you mean by that? Does Blender close? Or does the console itself close?
I think this is a really good thing to tackle. If not for Blender at
least for the blenderplayer.
* When you call blender/player from command-line the console should
always be there - *optionally when called by -c*
* When we call from a .bat or from an .exe blender/player shouldn't be
there (unless when called by -c [ though *optionally* it can be made
visible through the "show console" operator] ).
* When we call blender/player from an external process (os.suprocess
or the -i option) the console should show only when called with -c
Would that be possible?
2013/4/6 Alexandr Kuznetsov <kuzsasha at gmail.com>:
> Blender on Windows starts as console app and hides the console few
> seconds after the start.
> I reimlemmented, so Blender starts without any console. In addition,
> user can open console from Blender. The problem with this approach is
> that calling Blender.exe from cmd returns immediately. This might create
> some problems. I solved this by creating blendercmd.exe which set ups
> pipes properly and runs blendergui.exe, outputting as before. This might
> not be ideal solution for all.
> Here some versions:
> * Have only gui version
> * Have blender.exe as a terminal pipe setter which runs blendergui.exe.
> * Have blender.exe and and blendercmd.exe as a pipe setter.
> For both make default shortcut for gui app.
> * Redistribute two packages: one console app, another gui app. Make this
> a build option. (maybe we can even dynamically patch executable from one
> to another)
> * Leave it as it is
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers