[Bf-committers] New feature: Console output space type(requestfor input).

Gilbert, Joseph T. jgilbert at tigr.ORG
Thu Apr 20 18:29:43 CEST 2006


Well the real benefit of this is not having to switch to the other
window (or to the terminal) to see stdout, (which is a huge benefit to
the end-user), not just so you don't have 2 windows open on a windows
box. There's actually a lot of benefits to having stdout routed to a
screenarea than just aesthetics. For mac/linux users they can see script
errors and output inside blender rather than figuring out they need to
run blender from the commandline to see stdout.

Doing a better reading of the original mail: """I am not sure I can
enable the text to go to both at this stage""". :p If it can't be done
than yea, I think a commandline switch is an acceptable option. For
windows development this wouldn't matter at - just don't bring up that
window :). For linux/mac it would be nice to have stdout routed to the
terminal. Another way to do it Jacque would be to set up a preprocessor
macro like TERMINAL_STDOUT that can be enabled in debugging builds. Just
an idea :)


-----Original Message-----
From: bf-committers-bounces at projects.blender.org
[mailto:bf-committers-bounces at projects.blender.org] On Behalf Of Ewout
Fernhout
Sent: Thursday, April 20, 2006 12:05 PM
To: bf-blender developers
Subject: Re: [Bf-committers] New feature: Console output space
type(requestfor input).

> 1) You killed the output window.

wasn't that the whole purpose of this patch? That's what I like about
it (although I agree with others that it should be optional by command
line argument).

Ewout
_______________________________________________
Bf-committers mailing list
Bf-committers at projects.blender.org
http://projects.blender.org/mailman/listinfo/bf-committers


More information about the Bf-committers mailing list