[Bf-committers] Console on Windows Build

Campbell Barton ideasman42 at gmail.com
Mon May 17 11:23:20 CEST 2010


On Mon, May 17, 2010 at 11:16 AM, Joshua Leung <aligorith at gmail.com> wrote:
> None of the prints in question originate from py scripts
>
> On Mon, May 17, 2010 at 8:17 PM, Theo de Ridder
> <theo.de.ridder at planet.nl> wrote:
>>
>>
>> if printing is done through python,
>> there is no need for any console simply by redirecting like this:
>>
>> sys.stdout = bpy.data.texts.new('stdout')
>> sys.stderr = bpy.data.texts.new('stderr')
>>
>> ~Theo
>>
>>
>> On 17 mei 2010, at 06:24, bf-committers-request at blender.org wrote:
>>
>>>> Joshua Warner wrote:
>>>>> Please forgive me if this has already been discussed. ?Given that there is a
>>>>> "console" window type in the Blender 2.52 build, is there a potential for
>>>>> removing the console that launches alongside the main Blender window? ?This
>>>>> would make Blender fit in better with other Windows applications and also
>>>>> make it easier to manage multiple separate Blender instances.
>>>>>
>>>>
>>>> So long as the error messages that are thrown into the Windows console
>>>> are available somewhere for us to see when an import goes bad (or
>>>> similar), I think it would be good to do away with it myself.

this should be dealt with by blender reporting api, python has access
to this via operators currently.
-- 
- Campbell


More information about the Bf-committers mailing list