VI Server Property Information
|
Property ID
|
206
|
Scope
|
Basic Development Environment
|
Data Name
|
Exec.AllowDebug
|
Short Name*
|
Exec.AllowDebug
|
Long Name*
|
Execution:Allow Debugging
|
* Displayed here in English. Short and Long names appear in the language of the LabVIEW IDE.
|
Owning Class ID
|
2
|
Owning Class Name
|
VI Class
|
Data Type
|
Boolean data type
|
Property Node
|
|
Available in Real-Time Operating System | Yes |
Available in Run-Time Engine | Yes (Read Only) |
Available with control VIs | No |
Available with global VIs | No |
Available with polymorphic VIs | No |
Available with strict type definitions | No |
Loads the block diagram into memory | No |
Loads the front panel into memory | No |
Must wait until user interface is idle | No |
Need to authenticate before use | No |
Permissions | Read/Write |
Remote access allowed | Yes |
Settable when the VI is running | No |
If TRUE, you can use debugging tools on the VI. For example, you can set breakpoints, create probes, enable execution highlighting, and single-step through execution. Set this property to FALSE to disable use of debugging tools, reduce memory requirements, and to improve performance slightly for the VI.
This property is similar to the Allow debugging option on the Execution page of the VI Properties dialog box.
Note Writing this property causes the VI to be recompiled. Writing TRUE causes extra code and data to be generated for the VI. This code and data enables LabVIEW to set breakpoints and single-step through the VI. Writing FALSE removes this code and data, reducing the total size of the VI.
|
When you debug applications and shared libraries, you cannot debug reentrant panels that an Open VI Reference function creates. You also cannot debug reentrant panels that are entry points to LabVIEW-built shared libraries.
Uses
History
Version
|
Change(s)
|
|
More info to come.
|
See Also
External Links