FP Control inheriting the .ctl documentation

[Labviewguru]

I have a project in which I am using several typedefs and custom controls. I am doing documentation, and would like to have the FP controls and indicators inherit the documentation of typedefs and custom controls from the .ctl definition.

Does anyone know how to do this automatically? I could write a script to do this, but would rather see LabVIEW inherit that documentation where I defined the control/indicator.

Thank you

[Labviewguru]

Answer:

Try using the actual .ctl

This doesn't work with .ctl s when they are not typedefs.... If anyone knows how to get a control to inherit the .ctl documentation, I would be greatful.

Thanks

[JeanPierre]

Labviewguru,

If you did not save the control as a typedef, there is no link or connection
between the FP control instance and the control file. Therefore the
inheritance can't be done automatically. That is the typedef that links a
control to the file copy. I think you have no choice as to manually replace
all control instances by a typedef.

For typedefs, when you make "Apply Changes" in the control editor, the
description of subcontrols of the control are updated in the instances in
memory, but the description of the control itself stays unchanged in
instances. After all if you have different instances of a control it is
normal to allow different documentation.

Jean-Pierre Drolet

[David Thomson]

Labviewguru wrote:
>
> I have a project in which I am using several typedefs and custom
> controls. I am doing documentation, and would like to have the FP
> controls and indicators inherit the documentation of typedefs and
> custom controls from the .ctl definition.
>
> Does anyone know how to do this automatically? I could write a script
> to do this, but would rather see LabVIEW inherit that documentation
> where I defined the control/indicator.
>
> Thank you

On a similar note, it would be nice if there was an option such that
the instances of a type-def inherit the default value. Then when the
default value of the type-def was changed, the default value of each
instance would be updated. (I thought this was a feature in the LV 6
beta, but it ap
pears to be missing in the LV 6 release. Correct me if I
am wrong.)
Perhaps both these features could be bundled up into a new type of
type-def - super strict!

Regards,
Dave

-------------------------------------------------------------
David Thomson 303-499-1973 (voice and fax)
Original Code Consulting dthomson@originalcode.com
www.originalcode.com
National Instruments Alliance Program Member
-------------------------------------------------------------
Research Scientist 303-497-3470 (voice)
NOAA Aeronomy Laboratory 303-497-5373 (fax)
Boulder, Colorado dthomson@al.noaa.gov
-------------------------------------------------------------