BUG regarding input & outputs of C# component

I’ve recently been faced with an annoying problem when changing the inputs and outputs of a C# component inside Grasshopper. It seems that when editing any feature of inputs or adding new outputs to the component while the C# editor is open, the changes don’t apply, or don’t apply properly.

For example, in the screenshot below, I’ve changed the input from “Item Access” to “List Access”, but in the editor, the input is still “Item”, and in many other cases where I’ve changed the input properties or added outputs, I’ve faced this issue. Is there any fix for this, or is it a BUG?

2 Likes

Dear Rhino Support Team,

I can confirm that I have also encountered the bug reported by user @Mehrad_Mahnia regarding changes to the inputs and outputs of a C# component inside Grasshopper.

When modifying input properties (e.g., switching from “Item Access” to “List Access”) or adding new outputs or Input or change type of Geometry while the C# editor is open, the changes are not applied correctly or fail to take effect at all. This behavior not only disrupts workflow but also significantly slows down script development and testing in the C# ScriptEditor.

Please investigate this issue and provide a fix in an upcoming update.

Thank you for your support.

@eirannejad
@Alain

1 Like

Hi @Mehrad_Mahnia,

I am unable to reproduce. What SR of Rhino 8 are you using?

– Dale

Hi Dale;

I’ve updated my Rhino a few days ago, its now Rhino 8, SR22 … before updating I’ve encountered the issue as well, but it seems to become worse after updating … and the weird thing is that the issue occurs here and there, sometimes adding and editing input and outputs works fine, some times it doesn’t work properly (while the C# editor is open) … Today I realized that when this issue occurs, if I close the editor and recompute the C# component, the input/output I’ve added disappears as it has never been added!

1 Like

Dear @dale

I’ve recently upgraded my OS to Win11. Could this upgrade be related to the issue?

I’ve recorded my screen in one of the cases where this issue occurs, so you can see the weird behaviour of the C# editor.