I understand where you are going with this, but I think it breaks the syntax and consistency with other property and invoke nodes. Namely, the first block in the list is the name of the method or property, and the one you click on if you want to change it to something else. Your proposal makes it look like Control Name is the method being invoked since it is the item on top.
The name of the method isn't the name of the parameter. We only use the method name as an input terminal when the method name is able to be the name of the parameter. I won't guarantee that all of our nodes follow the pattern correctly, but this one does match our standard as it stands today. So of the three pictures you have in your original post, ouadji, I would mark the current behavior as "Best".
So... that's why the node is the way it is today. What exactly are you trying to fix by changing it? Maybe there's some other fix we can apply.
I don't understand your suggestion. Your scheme would require removing the name of each method in order to be consistent. What would you have when a method had no parameters? What would be the point of changing the name of the parameter "Value" with "CtrlVal.Set"? Is 'Value" so confusing?
We could change the Get function to have a Value terminal instead of using the method name as the terminal. Then they would match. Is the parallelism what you're after?
Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.