Python - Set Data Type of Inputs (Not Type Hint)

[michaelvollrath]

Hello,

How can I set the data type of inputs from within the python script?

I know I can wrap the python script in a cluster, and add nodes like “data” “boolean” etc in between the input and python input to then be able to “set” the inputs of the cluster, I would like to achieve this with the python component only.

Currently if I right click an input I can “set data item” but if this is a boolean for instance I want to see “set boolean” here instead.

Thanks for any help and leads!

Current:

Expectation:

[AndersDeleuran]

This might help:

GHPython Default Type Hint

I can appreciate that. But I guess I just don’t see how adding an option to set a default type hint locally by user preference would have such severe implications/high cost. That sounds good. I’ll take it On a side note (might help others), I added this function to my GHPython development utility functions module. Which I sometimes use to turn type hints off locally within one component, especially if I’m adding multiple inputs straight off the bat: import GhPython def setNoTypeHin…

[jsb.walker]

If you’re trying to create a component from scratch complete with custom control over UI elements, you’re not going to get that functionality from a single script component.

[michaelvollrath]

Thanks @AndersDeleuran I did come across your post in my findings earlier and perhaps I’m misunderstanding it or not phrasing my question correctly.

I am trying to achieve the following in a similar way to how ghenv.Component.Param.Input[0].Name = “Param Name Here” works

in the way that that specifies the name of the input i would like to specify the type as well, something like (making this up):

ghenv.Component.Param.Input[0].Type = Bool, False

where bool would set the input to type Boolean and the second value would set the default value to false.

this way when i drop the component on the canvas and right click the input i could set True or False as you can with native components.

Thanks for your help!

[michaelvollrath]

I see @jsb.walker , thank you. So I would need to go more the plugin development route then as the functionality is not available un a GH Python Script Component, am I understanding that corrrectly?

[jsb.walker]

As far as I’ve come across, yes, you need to use development tools to explicitly type the input of a component.

Though what you’re describing would be a helpful feature. I’d probably add user controlled explicit typing to clusters over scripting components. It shouldn’t be too difficult to have cluster components inherit the typing of the first casting component that the inputs are attached to or something.

[michaelvollrath]

Good to know and I believe cluster inputs/outputs do inherit the type/info of what they connect to which is nice. My current workflow has been to wrap python components inside a cluster and connect a node of the type i want in between the cluster input and the script input. This allows me to have “pretty” looking custom components and allows me to right click and set the input based on data type.

i just was hoping to be able to specify this directly in the scripting component so that im not wasting overhead or adding complexity by wrapping a perfectly functional script in a cluster.

[jsb.walker]

You’re right, I never noticed before but they do. I think that’s your easiest option for the functionality you’re looking for.

[AndersDeleuran]

Ah yes, I missed the setting of the data part, my bad. I think you need to fiddle with the parameter volatile data. This is for outputs, but have a look:

Set value of python component output / ghenv.Component.Params.Output[1].SetValue

[image] import Grasshopper as gh ghenv.Component.Params.Output[1].VolatileData.Clear() ghenv.Component.Params.Output[1].AddVolatileData(gh.Kernel.Data.GH_Path(0), 0, "Data") private void RunScript(object x, object y, ref object A) {} // <Custom additional code> public override void AfterRunScript() { Component.Params.Output[1].VolatileData.Clear(); Component.Params.Output[1].AddVolatileData(new GH_Path(0), 0, "Data"); } [AddVolatileData.gh|attachment](upload://gna4BvFDwIzEr4A4Hur3elEH95T…

That said, when I need a default input value I just check if the parameter variable is None (for item data) and then set the variable to the default value within the script (i.e. before running any code as part of the input checks). And then document this in the parameter docstring so the user knows what’s going on.

Edit: Jesus, sorry again. I understand now. And yes I think a compiled component is probably the way to go. Though I suspect one could do it when running a GHPython component in SDK mode.

[michaelvollrath]

@AndersDeleuran

Though I suspect one could do it when running a GHPython component in SDK mode.

ooo interesting! I turned on the SDK mode it appears to give me a “behind the scenes” look at some of the things defining the component in general but wondering what to search for in the API docs regarding setting input types?

What syntax do you use to define an input type in a compiled plugin component?

I can’t find any information in the API docs about setting input types

[AndersDeleuran]

@michaelvollrath

What syntax do you use to define an input type in a compiled plugin component?

Have a look at Giulio’s example here:

Creating a default value for a GHPY compiled component

Hi Marco @mp1 I moved the conversation to a new topic, so it might be useful also to other users. OK; then it makes sense. We need to dig a little deeper into the Grasshopper SDK. Here is how: def RegisterInputParams(self, pManager): p = Grasshopper.Kernel.Parameters.Param_String() self.SetUpParam(p, "matName", "matName", "Name of the material.") p.Access = Grasshopper.Kernel.GH_ParamAccess.item p.SetPersistentData(Grasshopper.Kernel.Types.GH_String("Test")) self.Params…

[michaelvollrath]

Perfect thank you, I’ll do some reading!