C# Custom Component

Hi,

Is it possible to know how to create component with Plus and minus buttons as scripting components?

I want to add the same type objects, and output them one by one depending of quantity of them.

Thanks

Replies to This Discussion

Permalink Reply by David Rutten on December 23, 2016 at 9:10am

Your component must then implement the IGH_VariableParameterComponent interface. Hopefully the 6 or so methods/properties required are reasonably self-explanatory.

Permalink Reply by Tomas Vinkevicius on December 23, 2016 at 10:27am

Thanks, I have it working. When I want to declare item list tree as input, what has to be changed and is it within this method?

IGH_Param IGH_VariableParameterComponent.CreateParameter(GH_ParameterSide side, int index)
{
Param_Plane param = new Param_Plane();
param.Name = GH_ComponentParamServer.InventUniqueNickname("PPPPPPPPPPPPPPPPPPPPPPPPPPPPP", Params.Input);
param.NickName = param.Name;
param.Description = "Plane" + (Params.Input.Count + 1);

return param;
}

Permalink Reply by David Rutten on December 23, 2016 at 12:51pm

I recommend making CreateParameter as simple as possible. Do all parameter property assignments in the Maintenance function, it gets called a lot more than CreateParameter. I'd suggest only having return new Param_Plane(); in CreateParameter().

Permalink Reply by Tomas Vinkevicius on December 23, 2016 at 10:29am

Found param.Access = GH_ParamAccess.list;

Permalink Reply by Tomas Vinkevicius on December 23, 2016 at 10:48am

What would be the logic for creating multiple outputs that contains one object per output?

For instance I have 1 list of numbers: 0 1 2 3 4, but it can be 0 1 2 or only one number.

In these cases components creates either 5 or 3 or 1 output, each containing one element of the list.

Permalink Reply by David Rutten on December 23, 2016 at 12:57pm

This is not a good idea to do automatically. People spend time and effort hooking up wires to parameters and they'd get cross if you just delete a parameter without asking them. This can easily happen when the user cancels a solution for example.

It's sort of ok to only add parameters and only ask to delete, but I recommend taking the ExplodeTree approach. Add an error/warning to the component if the output layout doesn't match up with the data, and add a menu item which fixes this.

Either way though, you cannot change the parameter layout during solutions. Adding/removing parameters to/from component can be done in either: