LabVIEW Wiki - User contributions [en]

LabVIEW configuration file/Miscellaneous

2009-08-08T03:16:46Z

Jgcode:

This is a list of Miscellaneous LabVIEW ini File settings. {{TOCright}}

{{ labviewconfigurationkey
| keyname = BldApp.RemovePolyVIsandTypedefs
| example =BldApp.RemovePolyVIsandTypedefs=FALSE
| datatype =b
| description =Setting this to <code>FALSE</code> stops the LabVIEW Application Builder from aggressively removing polymorphic VIs and typedefs that it thinks are not required
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 7
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =By default, the LabVIEW 7.x Application Builder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. This setting can be changed in the LabVIEW 7.1 applciation Builder in the Application Settings page.
If a VI in your build calls an external VI that uses a type definition in order to pass parameters, and the AppBuilder is unaware of this external VI, it will end in tears.
Also there is one other issue which makes this setting very important. In LabVIEW 7.x, by disconnecting typedefs from controls they did loose their default data and return to LabVIEWs default default data. This could be a major problem if you used strict typedefed clusters on front panels to provide certain default data when unwired and those default data did not match LabVIEWs default default data. This has been mostly fixed in newer LabVIEW versions from 8.0 on.
}}

{{ labviewconfigurationkey
| keyname = coerceFromVariant
| example =coerceFromVariant=TRUE
| datatype =b
| description =Force variants to automatically coerce to any data type that they are connected to
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Tread carefully, as using this function removes coercion notification, and does not use error handling
}}

{{ labviewconfigurationkey
| keyname = cleanupVisa
| example =cleanupVisa=TRUE
| datatype =b
| description =Automatically close VISA sessions - do not require the use of the ''VISA Close'' VI
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = defaultConPane
| example = defaultConPane=4833
| datatype = I32
| description = Sets the default [[Connector pane]] layout for new VIs
| permitted_values =
| default = (4815)
| LV1 = 8.x
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Source: NI Knowledge Base
( http://digital.ni.com/public.nsf/allkb/279F064F0688C114862570900057678C )
}}

{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype = i
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}

{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}

{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}

{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = showNoNavDialog
| example =showNoNavDialog=TRUE
| datatype =b
| description =Prevents the "Getting Started Window" dialog from appearing
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =
| OS4 =
| notes = Source: NI Knowledge Base ( http://digital.ni.com/public.nsf/allkb/841B934909D863C886256F62006AC243?OpenDocument )
}}

{{ labviewconfigurationkey
| keyname = ShowTipStrings
| example =ShowTipStrings=FALSE
| datatype =b
| description =Display Tip Strips during execution
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}

{{ labviewconfigurationkey
| keyname = skipNavigatorDialog
| example =skipNavigatorDialog=TRUE
| datatype =b
| description =Skip the navigation dialog on development environment launch
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = SuperPrivateSpecialStuff
| example =SuperPrivateSpecialStuff=TRUE
| datatype =b
| description =Exposes private properties, method and events in the IDE
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Not supported by NI, this is not a scripting method.
}}

{{ labviewconfigurationkey
| keyname = suppressFileDlgForMissingVIs
| example =suppressFileDlgForMissingVIs=TRUE
| datatype =b
| description =Suppresses the file dialog for when loading a VI that has missing SubVIs
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = useNativeFileDialog
| example =useNativeFileDialog=FALSE
| datatype =b
| description =Use the OS native file dialogs
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = userVIsAppearFirst
| example =userVIsAppearFirst=TRUE
| datatype =b
| description =Makes the user VIs appear first in the tool menu
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 6
| LV2 = 7
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Unfortunately this option no longer works in LabVIEW versions 8+.
}}

{{ labviewconfigurationkey
| keyname = XNodeWizardMode
| example =XNodeWizardMode=TRUE
| datatype =b
| description =Allows contextual menus on [[XNodes]] to facilitate debugging
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = MaxGSWRecentProjects
| example =MaxGSWRecentProjects=10
| datatype =i
| description =Allows more projects to be added to the Getting Started Window
| permitted_values = 1 to 10
| default = 2
| LV1 = 2009
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

[[Category:Configuration_File|Misc]]

LabVIEW object-oriented programming FAQ

2009-02-21T01:05:16Z

Jgcode: Updated and added method to "My LVOOP control has black border" to set the default data of a LVOOP constant

This is a stub page for Frequently Asked Questions (FAQ) about LVOOP. Please feel free to add to the list of FAQ and answer any of the questions that have been posted.

You may find many questions already answered on the [http://zone.ni.com/devzone/cda/tut/p/id/3573 LVOOP FAQ on NI's website]. That FAQ will be updated by NI for new versions of LabVIEW and new OO tools as they become available.

== Why is class data private? ==

In general object-oriented programming terms, attributes (like methods) can have private, protected, or public visibility. In practice individual object-oriented programming languages have differing capabilities when it comes to specifying visibility. In the UML attributes are generally assumed to have private visibility unless otherwise specified. (Operations, on the other hand, are assumed to be public unless otherwise specified.) Generally, OOP style guides say never to give attributes public visibility, and the so-called “Law of Demeter” in its strong form limits attribute visibilities to private. In other words, access to data in a class from outside the class is always through accessor methods (‘set’ or ‘get’) methods. In LVOOP this is the only choice, a decision designed to promote good code designs with minimal coupling. (See further here: [http://zone.ni.com/devzone/cda/tut/p/id/3574]). (Note that LabVIEW 8.5 introduces a “Create Accessor” dialog box to simplify the creation of accessor methods. For more information on this dialog box see the LabVIEW 8.5 Upgrade Notes here: [http://digital.ni.com/manuals.nsf/websearch/7A60FDCEA6D2D8C4862572FD00159F5A].)

== What are the differences between public, protected, and private class members? ==

In Object-Oriented Programming terms these generally mean:

A private feature (UML abbreviation -) is accessible only from the defining class. A public feature (+) is accessible from outside the class. A protected feature (#) is (in C++, for example) accessible from the defining class and any of its child classes. The UML also has an abbreviation for package (~) visibility. The exact meaning of the different visibilities varies among different programming languages.

== Why are there no class constructor and destructor? ==

== Are objects by value or by reference? ==

== What does LVOOP mean? ==

== How can I create by reference objects? ==

== How can I create active objects? ==

== Are there any add on tools for LVOOP? ==

== What does the "Dynamic Dispatch" connector pane terminal setting do? ==

== My LVOOP class control has a black border, what does that mean ? ==

A LVOOP class has a default value that is determined by the default value of the private data control in the .lvclass file. However, a control on a vi front panel, or a constant on a block diagram can also have a default value that is different from the default data for the class as a whole. When this happens the control (or constant) is given a black border. It can just as easily be a non-default value of the class itself, so if your private data cluster contains a numeric whose default value is 5, this control may have the numeric with a default value of 6.

When there is a class heirarchy, it is possible for a parent class method to process an instance of a child class. Similarily, it is possible to set the default value of a parent class control or constant to be an instance of a child class. This will also result in a black border around the parent class control or constant. When this happens with a member vi of the parent class, the parent class becomes dependent on the child class in addition to the normal dependency of the child on the parent. This can be confusing and awkward to locate.

To change the default value of a class control run a VI such that a non-default value ends up in an indicator, then do one of the following: A) Right click on that indicator and choose "Make Current Value Default" or B) Right click on that indicator and choose "Change to Constant" (the current value of a control/indicator always becomes the value of the constant)

[[Category:GOOP]]

[[Category:GOOP]]

LabVIEW Books

2009-02-05T22:17:44Z

Jgcode: Corrected year from 20 to 2008 on Lego Book

*'''The LabVIEW Style Book'''[http://www.amazon.com/LabVIEW-National-Instruments-Virtual-Instrumentation/dp/0131458353/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1222260054&sr=8-1] Prentice Hall, 2007 Blume, Peter.
*'''A Software Engineering Approach to LabVIEW''' [http://www.amazon.com/Software-Engineering-Approach-Instruments-Instrumentation/dp/0130093653/ref=sr_1_1?ie=UTF8&s=books&qid=1222260141&sr=1-1] Prentice Hall, 2003 Conway, Jon, and Watts Steve.
*'''LabVIEW for Everyone Graphical Programming Made Easy and Fun (3rd Edition)''' [http://www.amazon.com/LabVIEW-Everyone-Programming-Instruments-Instrumentation/dp/0131856723/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1222260178&sr=1-1] Prentice Hall PTR, 2006 Travis, Jeffery, and Kring, Jim.
*'''LabVIEW Advanced Programming Techniques Second edition''' [http://www.amazon.com/LabView-Advanced-Programming-Techniques-SECOND/dp/0849333253/ref=sr_1_1?ie=UTF8&s=books&qid=1222260218&sr=1-1] CRC Press, 2007 Bitter Rick, Mohiuddin, Taqi, and Nawrocki, Matt. 
*'''LabVIEW Basics I and II''', '''LabVIEW Intermediate I and II''', '''LabVIEW Advanced I'''[http://sine.ni.com/nips/cds/view/p/lang/en/nid/10292] National Instruments Course Kits
*'''Hands On Introduction to LabVIEW for Scientist and Engineers''' [http://www.amazon.com/dp/0195373952/ref=pe_606_11251780_pe_ar_t1] Oxford University Press, 2008 Essick, John.
*'''LabVIEW for LEGO MINDSTORMS NXT''' [http://www.amazon.com/dp/0195373952/ref=pe_606_11251780_pe_ar_t1]  NTS Press 2008 Gasperi, Michael.

== External links ==

*National Instruments book list: [http://zone.ni.com/devzone/cda/tut/p/id/5072 http://zone.ni.com/devzone/cda/tut/p/id/5072] 
*Scott Hannah's book list: [http://hannahsmac.magnet.fsu.edu/labview/basic_labviewbooks.html http://hannahsmac.magnet.fsu.edu/labview/basic_labviewbooks.html] 

 

[[Category:LabVIEW_fundamentals]] [[Category:Books]]

LabVIEW Books

2009-02-05T14:00:24Z

Jgcode: Added book LabVIEW for LEGO MINDSTORMS NXT

Blume, Peter. '''The LabVIEW Style Book'''[http://www.amazon.com/LabVIEW-National-Instruments-Virtual-Instrumentation/dp/0131458353/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1222260054&sr=8-1] . Prentice Hall, 2007

Conway, Jon, and Watts Steve. '''A Software Engineering Approach to LabVIEW''' [http://www.amazon.com/Software-Engineering-Approach-Instruments-Instrumentation/dp/0130093653/ref=sr_1_1?ie=UTF8&s=books&qid=1222260141&sr=1-1] Prentice Hall, 2003

Travis, Jeffery, and Kring, Jim. '''LabVIEW for Everyone Graphical Programming Made Easy and Fun (3rd Edition)''' [http://www.amazon.com/LabVIEW-Everyone-Programming-Instruments-Instrumentation/dp/0131856723/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1222260178&sr=1-1] Prentice Hall PTR, 2006

Bitter Rick, Mohiuddin, Taqi, and Nawrocki, Matt. '''LabVIEW Advanced Programming Techniques Second edition''' [http://www.amazon.com/LabView-Advanced-Programming-Techniques-SECOND/dp/0849333253/ref=sr_1_1?ie=UTF8&s=books&qid=1222260218&sr=1-1] CRC Press, 2007

National Instruments Course Kits '''LabVIEW Basics I and II''', '''LabVIEW Intermediate I and II''', '''LabVIEW Advanced I'''[http://sine.ni.com/nips/cds/view/p/lang/en/nid/10292]

Essick, John. '''Hands On Introduction to LabVIEW for Scientist and Engineers''' [http://www.amazon.com/dp/0195373952/ref=pe_606_11251780_pe_ar_t1] Oxford University Press, 2008

Gasperi, Michael. '''LabVIEW for LEGO MINDSTORMS NXT''' [http://www.amazon.com/dp/0195373952/ref=pe_606_11251780_pe_ar_t1] NTS Press 2008

 

 National Instruments has a [http://zone.ni.com/devzone/cda/tut/p/id/5072 Books and Publications list] (unfortunaltely a bit out of date) , a more recent book list can be found on [http://hannahsmac.magnet.fsu.edu/labview/basic_labviewbooks.html Scott Hannahs' website]. 

[[Category:LabVIEW_fundamentals]]

LabVIEW Books

2009-02-05T13:50:57Z

Jgcode: Added Hands On Introductioin to LabVIEW for Scientist and Engineers book

Blume, Peter. '''The LabVIEW Style Book'''[http://www.amazon.com/LabVIEW-National-Instruments-Virtual-Instrumentation/dp/0131458353/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1222260054&sr=8-1] . Prentice Hall, 2007

Conway, Jon, and Watts Steve. '''A Software Engineering Approach to LabVIEW''' [http://www.amazon.com/Software-Engineering-Approach-Instruments-Instrumentation/dp/0130093653/ref=sr_1_1?ie=UTF8&s=books&qid=1222260141&sr=1-1] Prentice Hall, 2003

Travis, Jeffery, and Kring, Jim. '''LabVIEW for Everyone Graphical Programming Made Easy and Fun (3rd Edition)''' [http://www.amazon.com/LabVIEW-Everyone-Programming-Instruments-Instrumentation/dp/0131856723/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1222260178&sr=1-1] Prentice Hall PTR, 2006

Bitter Rick, Mohiuddin, Taqi, and Nawrocki, Matt. '''LabVIEW Advanced Programming Techniques Second edition''' [http://www.amazon.com/LabView-Advanced-Programming-Techniques-SECOND/dp/0849333253/ref=sr_1_1?ie=UTF8&s=books&qid=1222260218&sr=1-1] CRC Press, 2007

National Instruments Course Kits '''LabVIEW Basics I and II''', '''LabVIEW Intermediate I and II''', '''LabVIEW Advanced I'''[http://sine.ni.com/nips/cds/view/p/lang/en/nid/10292]

Essick, John. '''Hands On Introduction to LabVIEW for Scientist and Engineers''' [http://www.amazon.com/dp/0195373952/ref=pe_606_11251780_pe_ar_t1] Oxford University Press, 2008

 

 National Instruments has a [http://zone.ni.com/devzone/cda/tut/p/id/5072 Books and Publications list] (unfortunaltely a bit out of date) , a more recent book list can be found on [http://hannahsmac.magnet.fsu.edu/labview/basic_labviewbooks.html Scott Hannahs' website]. 

[[Category:LabVIEW_fundamentals]]