[Bf-committers] FW: console window back to appear

Doug Hammond doug.hammond at luxrender.net
Tue May 10 19:51:17 CEST 2011


The LuxRender addon prints version info to console at startup. Will I have
to silence the addon now? I'd rather not, since when asking users to report
issues, it is important we get as much info as possible from their console
outputs.

Doug,

On Tue, May 10, 2011 at 4:42 PM, Alexander Kuznetso <kuzsasha at gmail.com>wrote:

> Before the checking code was before python initialization. Now it is after
> due to taskbar problem of early hiding of the window.
> Also I think it is fine if console stays when Python error occurs, so user
> would be notified.
>
> Sent from my phone
>
> On May 10, 2011, at 9:27 AM, Yousef Hurfoush <bat3a at msn.com> wrote:
>
> >
> >> 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 error, which gets printed to the
> >> console, thus prevents the console from being closed. Do check any of
> >> the other addons if they print anything during startup (imo they
> >> shouldn't if there are no errors).
> >>
> >
> > they do print.
> >
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
Doug Hammond (dougal2),
Developer and Admin for


More information about the Bf-committers mailing list