Not sure about what you would get with 100's of functions in the dll? The current right-click menu offers acess to all that info quite efficiently in my opinion...
I think this idea is only asking for information about the currently selected function. You would use the right-click menu to change functions/view more information as always.
After messing around with drivers that were nothing but CLFs, I would gladly have this. Just a little extra information (the current DLL and the function being called) in the context help would save me tons of time. Currently, you have have open a dialog just to see what's being called. Quite annoying when performing a massive debug effort.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions Unofficial Forum Rules and Guidelines "Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
I would say that if anything, this should be on the BD, but I can say from experience that replacing the label with the function name is often too intrusive, because the function names tend to be long.
I like the idea. As a short term workaround, you can show the label on the Call Library Node, which displays the function name. I tend to always do that for Call Library Nodes these days for this reason.
One of the reason I would like to have this feature implemented is that the Call Library Function node becomes a "black box" while the code is running .
If the label has not been shown before starting the execution there's no way to see which function is being called (without stopping the code).
Kudos to the idea. And just in case not everyone is aware of it, if one right-clicks the Call Library Function node and selects "Name Format>>Names" then the node displays both the function name and the names of all the parameters. I set all CLNs this way for clarity.
