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 <shaul.ke...@gmail.com> 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 > <doughamm...@hamsterfight.co.uk> 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 > > 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
