You should use the reporting API for that. It logs to the internal console, so users will be able to copy/paste and whatnot.
Martin --- On Tue, 2/1/11, Doug Hammond <[email protected]> wrote: > From: Doug Hammond <[email protected]> > Subject: Re: [Bf-committers] [Bf-blender-cvs] SVN commit: > /data/svn/bf-blender [34590] trunk/blender/source/blender/ python/intern: > workaround [#25845] Empty UI panels > To: "bf-blender developers" <[email protected]> > Received: Tuesday, February 1, 2011, 2:23 PM > Another side effect of this is that > it's no longer possible to call my UI > message operator if something goes wrong with the render > process. I'm forced > to revert to printing to console, which many of our users > are unable to find > or copy/paste from correctly (example: > http://www.luxrender.net/forum/viewtopic.php?f=13&t=5369 > ). > > So, some new way to cause UI messages to appear would be > great ;) > > Cheers, > Doug. > > > On 1 February 2011 18:07, Shaul Kedem <[email protected]> > wrote: > > > > Please please, for the sake of everyone's sanity, > start communicating to > > the > > > API users before changing it. > > > > I think there should be a dedicated mailing list for > changes in the > > python API. Even if it is not stable or official yet, > it's a de-facto > > API and people are using it. > > > > On Tue, Feb 1, 2011 at 12:57 PM, Doug Hammond > > <[email protected]> > wrote: > > >> > > >> Though it should be quite simple to fix > things without duplicate code > > >> in your case, by making a function that both > the operator and render > > >> engine call? > > >> > > > > > > Yes, indeed this is what I've done - in fact the > refactoring is not as > > big > > > an issue as the lack of communication here and > the fact that I end up > > having > > > several addon users complaining at me that things > have stopped working > > every > > > time this happens! > > > > > > Please please, for the sake of everyone's sanity, > start communicating to > > the > > > API users before changing it. > > > > > > Doug. > > > _______________________________________________ > > > Bf-committers mailing list > > > [email protected] > > > http://lists.blender.org/mailman/listinfo/bf-committers > > > > > _______________________________________________ > > Bf-committers mailing list > > [email protected] > > http://lists.blender.org/mailman/listinfo/bf-committers > > > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
