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.com>wrote: > 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 > <doug.hamm...@luxrender.net> wrote: > > 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 <kuzsa...@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 <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 > >> > > > > > > > > -- > > Doug Hammond (dougal2), > > Developer and Admin for > > _______________________________________________ > > Bf-committers mailing list > > Bf-committers@blender.org > > http://lists.blender.org/mailman/listinfo/bf-committers > > > > > > -- > - Campbell > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > -- Doug Hammond (dougal2), Developer and Admin for _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers