Add documentation to a control/indicator created from external code (DLL or .NET Assembly) tied objects automatically

[Andreas_Pfichner]

Properties or parameters of methods are often documented (context help ctrl+h, move mouse over properties/methods). When a control is created to apply data to a property node or a method parameter, the available documentation of a property/method parameter should automatically be added to the controls documentation (description).

Example: The following picture shows a subVI of a LabView driver basing on an Ag3352x IVI-COM driver. Documentation for the amplitude property is available. When the amplitude control is created, the available documentation should be added automatically to the controls description...

[oenk]

This should also apply to loaded .NET code

fooClass in Visual Studio 2010:

fooClass in LabVIEW 2010:

[G-Money]

If no one objects, I am going to change the title of this idea to reflect the idea a little better. I see the idea overall as populating controls and indicators built from external code. This would involve parsing the dll or .NET assembly for documentation added. I think it is a good idea. I don't know if it is possible or not but hopefully changing the title will bring more traffic to decide whether they like the feature or not.