|LabVIEW 2016 Help|
|LabVIEW 2017 Help|
|LabVIEW 2018 Help|
|LabVIEW 2019 Help|
|LabVIEW 2020 Help|
You can configure access settings for items and folders that a LabVIEW project library owns as public or private. If you set an item as private and lock the project library, the item is not visible in the project library or in palettes. You cannot use a private VI as a subVI in other VIs or applications that the project library does not own, even if the project library is unlocked.
Determine which items in the project library you want to set as public and which as private. Public items might include palette VIs, XControls, instrument drivers, and other tools you want users to find and use. Private items might include support VIs, copyrighted files, or items you might want to edit later without taking the risk of breaking users' code.
You can set the access of a project sublibrary file (.lvlib) as private within the owning project library, but when you edit the project sublibrary itself, items the sublibrary owns retain public or private access settings.
Complete the following steps to configure access options in a project library.
|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.|
|Note You can set individual instances of a polymorphic VI as private and set the primary polymorphic VI as public. The polymorphic VI does not break even though instance VIs are private. Setting instance VIs as private is useful if you want users to access instances only through the polymorphic VI selector, so you can edit instance order without causing user problems.|
Items set as private appear in the Project Explorer window with a private icon . If you lock the project library, private items do not appear in the Project Explorer window.
You also can use the Source Scope:Set method to configure access options programmatically.