Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

Item Settings Page (Class Properties Dialog Box)

LabVIEW 2013 Help

Edition Date: June 2013

Part Number: 371361K-01

»View Product Info

Requires: Base Development System

Use this page of the Class Properties dialog box to configure the access settings for items that a LabVIEW class owns.

This page includes the following components:

  • Contents—Displays all components associated with the LabVIEW class. The tree displays the private data control and all the member VIs that the LabVIEW class owns. Click an item in the Contents tree to select it.
  • Localized Short Name—Specifies the name that a Property Node using Name Format»Short Names displays when you access the selected property.

    If Localized Short Name matches the name of the folder, LabVIEW automatically updates this field when you change the folder name. However, if you change this field, LabVIEW does not update the folder name.

    This field appears only if you select a property folder in the Contents tree.
  • Localized Long Name—Specifies the name that a Property Node using Name Format»Long Names displays when you access the selected property. This name also appears in the property selection menu that appears when you click the Property Node to select a property.

    If you include a colon in the Localized Long Name, the property selection menu includes a submenu for the information following the colon.

    If Localized Long Name matches the name of the folder, LabVIEW automatically updates this field when you change the folder name. However, if you change this field, LabVIEW does not update the folder name.

    This field appears only if you select a folder in the Contents tree.
  • Path—Displays the path to the item you select in the Contents tree.
  • Default Palette—Appears when you select a palette file (.mnu) in the Contents tree. Place a checkmark in the checkbox to set the file as the default palette for the LabVIEW class. Child classes do not inherit palettes from parent classes. If you want the same default palette in a child class that the parent class has, you must add the palette to the child class.
    Note  If you previously set a default palette in the Default Palette listbox on the General Settings page, a checkmark appears in the checkbox next to the default palette file. If you use this checkbox to change the default palette, the new default also appears in the Default Palette listbox.
  • Access Scope—Displays the access setting for the item you select in the Contents tree.
    Note  The Access Scope option must be the same in a parent dynamic dispatch member VI and a child dynamic dispatch member VI.
    • Public—The item is visible when users view the LabVIEW class. Other VIs and applications can call public VIs.
    • Community—The item is visible when users view the LabVIEW class. Only friends and VIs within the project library can call community VIs.
    • Protected—The item is visible when users view the LabVIEW class. Only other member VIs in the same LabVIEW class as the protected member VI, or a descendant class, can call a protected member VI.
    • Private—The item is not visible when users view the project library if you lock the LabVIEW class. Only other member VIs in the same LabVIEW class as the private member VI can call a private member VI.
    • Not specified—This option appears only when you select a folder. The folder does not have access items specified. Access is public. By default, folders in a class do not have access specified, which means the folders are publicly accessible.

      Note  If you specify access options for a folder, the access setting applies to all items in the folder and overrides access options for individual items in the folder.
  • Require descendant classes to override this dynamic dispatch VI—Place a checkmark in this checkbox to require any child class to define an override VI of the VI you select. This checkbox is available only if you select a dynamic dispatch VI in the Contents tree.

    You also can use the Descendants Must Override Item?:Set method to require descendant classes to override the dynamic dispatch VI programmatically.
  • Require overrides of this dynamic dispatch VI to always invoke the Call Parent Node—Place a checkmark in this checkbox to require that all dynamic dispatch VIs that override the specified VI to invoke the Call Parent Method node. This checkbox is available only if you select a dynamic dispatch VI in the Contents tree.

    You also can use the Descendants Must Call Parent Item?:Set method to require override VIs invoke the Call Parent Method node programmatically.

 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit