Is there a way to bold inputs and outputs in the VI documentation?

[Aaron02]

Context help for a VI shows the VI icon and terminals with the VI's documentation.  Some VI's documentation is constructed so that Input and Output names always appear in bold.   (for example, see the context help for list directory).   The attached image shows the context help for a VI I made.  I would like to have the documentation look like this:

Searches for all files in directory path that fit pattern.  Returns  arrays of all the file paths -- FilesMatchingPattern, filenames --FileNamesMatchingPattern and of a cluster containing both values -- StringsAndValues for files that match the given pattern

instead of like this:

Searches for all files in the directory path that fit pattern.  Returns  arrays of all the file paths (FilesMatchingPattern), filenames (FileNamesMatchingPattern) and of a cluster containing both values (StringsAndValues) that match the given pattern

[Chaos]

When setting up the VIs connector pane you should make the inputs/outputs you want bolded to be required which, I believe, is not the default...

[Aaron02]

True, you can set inputs and outputs as required, recommended, or optional -- but I want to make the documentation bolded -- the inputs and outputs in the text below the icon.  (see image and compare to the above image )

[LV_Pro]

This is an example of how to <B> bold </B>

P.M.

P.S. Please post as .jpg or .png rather than .bmp for bandwidth reasons (there are still some who are doing this over dialup)

Message Edited by LV_Pro on 10-05-2005 01:54 PM

[Chaos]

Ahha.  Actually I thought it would do this auto-magically but I guess not.  According to the documentation (on the documentation ) you can enclose any text you like in tags <B> and </B> to bold it... Cheers!

[Aaron02]

Thanks!  I look forward to implementing this

[Marinica]

Is there the possibility to set italic text also?

[Hooovahh]

---

@Marinica wrote:

Is there the possibility to set italic text also?

---

12 years.

Also as far as I know there is no way to do this.  But with NXG NI has a larger priority on documentation, and the VI descriptions supports what appears to be a full web browser of functionality, so it is something NI wants to improve.