> Also I think it is fine if console stays when Python error occurs, so user > would be notified. no,i think the default behavior should be making the > console hidden, if the user wants to debug, he can open it,most artists don't > need that. what happened to the idea of routing the external 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 > > 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 <ba...@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@blender.org > > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
