On 4/23/08, Joaquín Duo <
hoakoduo@...> wrote:
> I guess properties should be like this (see my example)
> input_mesh (like any other modifier, so it will be automatically connected,
> not
> input_mesh1)
> input_mesh1 already "coded"
I am currently reimplementing the MergeMesh plugin in C++. The
polyhedra part is in SVN now, and has k3d::imulti_mesh_sink in its
interface list. This means you just need to select a bunch of meshes
and apply the MergeMesh modifier from the right-click menu. The UI
code in k3dsdk/ngui/modifiers.h/cpp (modify_selected_meshes function)
will then create and connect a user property for each selected mesh.
I agree simply naming them input_1, ... was a mistake, though. Using
input_mesh1 and so on is clearer. Another possibility would be to use
the name of the node we are connecting to?
regards,
--
Bart
-------------------------------------------------------------------------
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