-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.5.2011 1:46, Yousef Hurfoush wrote:
i checked with luxrender, yafaray, index visualizer, ... many external addons
have the same impact on startup even without errors,
just removing them from the addons folder no startup console.
I
On Tue, May 10, 2011 at 9:18 AM, Nathan Letwory
nat...@letworyinteractive.com wrote:
index visualiser has currently an error, which gets printed to the
console, thus prevents the console from being closed.
Thanks for the report. Just committed a fix to SVN for the index visualiser
add-on
I haven't tried these yet, but if any code manages to print anything to
the console before the checking code is triggered then the console
doesn't close.
previously that was OK and did not trigger the console windows even with
errors, what happened???
index visualiser has currently an
console errors to the inner
console window, wouldn't that end this problems.?!!!
what about Linux version does it have the same problem ?
From: kuzsa...@gmail.com
Date: Tue, 10 May 2011 11:42:39 -0400
To: bf-committers@blender.org
Subject: Re: [Bf-committers] FW: console window back to appear
We could have the 'Help - System Info' script loop over addons and
include strings from an info() function.
this way you can ask users for 'System Info' output, its overkill just
for the version but there are probably other paths useful to include.
On Tue, May 10, 2011 at 5:51 PM, Doug Hammond
I like that idea.
More commonly though we want the console log for any python back-trace, and
having the addon info there keeps it in the same place and is less of a
process/ordeal for the user to deal with.
On Tue, May 10, 2011 at 11:48 PM, Campbell Barton ideasma...@gmail.comwrote:
We could
On Wed, May 11, 2011 at 9:32 AM, Doug Hammond
doug.hamm...@luxrender.net wrote:
I like that idea.
More commonly though we want the console log for any python back-trace, and
having the addon info there keeps it in the same place and is less of a
process/ordeal for the user to deal with.
i checked with luxrender, yafaray, index visualizer, ... many external addons
have the same impact on startup even without errors,
just removing them from the addons folder no startup console.
the official ones don't give any problem.
i think something in the recent commits that caused this,
