Bart Janssens wrote:
> On 4/26/08, Joaquín Duo <
hoakoduo@...> wrote:
>> When applying it as a Modifier it doesn't create a new MeshInstance. You may
>> change this anyway without making it a mesh_modifier.
>
> There is still the problem of the transformations of the inputs. If
> you don't keep the original MeshInstance, they are lost. For plugins
> like MergeMesh and boolean operations, this is not intuitive. That's
> why the connection is now made to the transformed_mesh property of the
> instance.
Ups, I forgot about this.
My opinion: In order not to confuse the user MergeMesh shouldn't hide the source
node (since the user could press "show all", then it's lost). There should be a
separate option, a script by now, that disables them from render on Renderman or
the Viewport. (setting the painter to None, i can do it)
Cheers!
Joaquín
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development
