Library class/Contains Compiled Code property: Difference between revisions
Appearance
Added new property page. |
(No difference)
|
Revision as of 04:41, 3 April 2020
| VI Server Property Information | |
|---|---|
| Property ID | 4D10E826 |
| Scope | Basic Development Environment |
| Data Name | ContainsCompiledCode |
| Short Name* | ContainsCompiledCode |
| Long Name* | Contains Compiled Code |
| * Displayed here in English. Short and Long names appear in the language of the LabVIEW IDE. | |
| Owning Class ID | 80 |
| Owning Class Name | Library Class |
| Data Type | Boolean data type |
| Property Node | |
| Available in Real-Time Operating System | No |
| Available in Run-Time Engine | No |
| Loads the block diagram into memory | No |
| Loads the front panel into memory | No |
| Need to authenticate before use | No |
| Permissions | Read/Write |
| Remote access allowed | Yes |
| Settable when the VI is running | No |
Sets or returns whether LabVIEW stores the library in the compiled object cache.
If TRUE, LabVIEW does not store the library in the compiled object cache. In this case, you must save the library every time you modify a member of the library or when you migrate the library to a new version of LabVIEW. If FALSE, LabVIEW stores the library in the compiled object cache so you must save the library only when you change the library itself.
This property is similar to the Separate compiled code from source file option on the General Settings page of the Project Library Properties dialog box.
Uses
| |
Specific use cases for this property. |
History
| |
History information is needed. What changes have occurred over previous versions? |
| Version | Change(s) |
|---|---|
| More info to come. |
See Also
| |
Add links to internal wiki pages that would also help. |
External Links
| |
Add links to external resources that would also help. |