[Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [34914] trunk/blender/release/scripts/ui/ properties_material.py: Commit patch [#25939] material panel proposal by Ervin Weber (lusque).

[Matt Ebb]

On Friday, February 18, 2011, Ton Roosendaal <ton at blender.org> wrote:

> Whether you like it or not, it's how the system works.

The trouble is though that there are more idiosyncracies and hidden
complexities in the system than just these, that this new organisation
doesn't express clearly. You end up running up against these when you
try to use it anyway- for example the odd refraction behaviour in node
trees and how some of the raytracing related settings (eg transmission
settings) only take effect from the parent material container and not
sub-material-materials. So should these be reflected in the ui too? I
think it would be worse if it were.

That's what I mean by saying if you want to represent the internal
system accurately, the ui will make less and less sense.

Matt