[Bf-committers] Python callbacks and keeping properties in sync

Doug Hammond doughammond at hamsterfight.co.uk
Tue Mar 29 00:05:59 CEST 2011

I've also seen too that there were plans to get this implemented around
about now.
(It was suggested in meeting minutes some weeks ago to be done in March?).

Campbell has also admitted that he's got some of the code for it already
written, and
it is really about time this became implemented, us python devs have been
forever (it seems).

So, any chance to get this before the stable release ?


On 28 March 2011 12:55, Wenzel Jakob <wenzel at wazlaf.org> wrote:

> Hello all,
> I am currently designing a rendering backend that integrates Mitsuba (a
> physically based renderer) with Blender 2.56a based on Doug Hammond's
> extensions framework.
> One of the issues I am periodically facing is synchronization between
> the Blender and Mitsuba interpretations of the scene. For instance,
> Blender Internal and Mitsuba have wildly different material
> configurations, and hence the rendering plugin adds custom UI panels to
> configure all materials.
> However, there is still a bit of overlap with Blender Internal. It would
> be great if it was possible to "react" to property changes in a material
> so that they can be forwarded to the other respective material
> implementation (where it makes sense). For instance: if the user
> specifies a diffuse gray BI material, that could easily be replicated in
> the Mitsuba material panel.
> I remember that somebody was working on Python-based property callbacks,
> which could potentially be used to implement such a feature. I'm curious
> to hear about the state of this work.
> Thank you,
> Wenzel
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list