LabVIEW Wiki - User contributions [en]

Connector pane

2024-05-29T14:50:27Z

Thoric: typo fix

{{TOCright}}
The '''Connector Pane''' is used to pass data to and from a [[SubVI]]. The Connector Pane is available in the [[Front Panel]] window's upper right corner next to the [[VI Icon]].

== Patterns ==
Right-click on the Connector Pane to choose a pattern.

[[Image:Connector Pane Patterns.png|thumb|center|300px|How to select a connector pane pattern]]

It is considered good practice to choose a pattern that has more inputs/outputs than you need when writing the VI so that new inputs or outputs can be added without changing the connector pane and causing the VI's that link to your subVI to recompile. The 4x2x2x4 pattern highlighted above is the most commonly used for NI primitives. In [[LabVIEW 8]] and above the connector pane is defaulted to the 4x2x2x4 pattern. To customize the default connector pane used for new VIs, set the defaultConPane variable in your [[LabVIEW configuration file]] (see [[LabVIEW configuration file/Miscellaneous#defaultConPane|Miscellaneous>defaultConPane]]).

[[Image:ConPane.png|center|Connector pane values]]

=== Increase/Decrease Terminals ===
Right-clicking the Connector Pane and selecting '''Add Terminal''' or '''Remove Terminal''' effectively moves the pattern up or down one.

=== Changing Orientation ===
Right-clicking the Connector Pane and selecting '''Rotate 90 Degrees''', '''Flip Horizontal''', or '''Flip Vertical''' keeps the same pattern but changes the orientation.

== Connecting Controls and Indicators ==
To connect a control or an indicator to a terminal on the Connector Pane:
# Select the control or indicator
# Click on the desired terminal on the Connector Pane

== Switching Terminal Positions ==
To switch or move a control or indicator to a different terminal:
# Click on the terminal to move on the Connector Pane
# Hold-down ''Ctrl'' and click on a different terminal. This will switch the two terminals, whether connected to something or empty.

== Disconnecting a Terminal ==
Right-click on the Connector Pane and select either:
* '''Disconnect All Terminals''' - to disconnect all terminals
* '''Disconnet This Terminal''' - to disconnect just the terminal that was clicked on

== Requirement Level ==
Right-clicking a terminal and selection '''This Connection Is''' presents four different options. The terminals can be set to:
# '''Required''' - sets the input as required. If the input is not wired, the program will not run, see [[Broken Run Arrow]].
# '''Recommended''' - sets the input as recommended. If the input is not wired, the program will still run and the default value for control is used.
# '''Optional''' - sets the input as optional which is the same as recommended but the terminal will not appear in the [[Context Help]].
# '''Dynamic Dispatch Input (Required)''' or '''Dynamic Dispatch Output (Recommended)''' - Greyed out except for [[Class (object-oriented programming)|class]] inputs and outputs. Sets the [[VI]] as [[Dynamic dispatch]].

== Index of Terminals ==
When using [[VI Scripting]] to access a Connector Pane (for example: [[ConnectorPane class/Controls() property|ConnectorPane class/Controls[] property]]), the terminals by defaultare ordered from Right to Left, Bottom to Top. This changes if the pattern is rotated or flipped. Therefore, for a standard 4x2x2x4 pattern the terminals are indexed as follows:

[[File:4x2x2x4-Default.png|Default 4x2x2x4]]

To see other patterns, see [[Connector pane patterns|Connector Pane Patterns]].

== Best Practices ==

=== Terminal Organization ===
* Use the 4x2x2x4 pattern even if it leaves empty spaces. Only go to patterns with more terminals if necessary. However, before switching to more terminals, consider [[Bundle|bundling]] inputs or outputs into [[Cluster data type|Clusters]].
* Put inputs on the left side of the Connector Pane and outputs on the right.
* Use the bottom corners for ''[[Error Cluster data type|error in]]'' and ''[[Error Cluster data type|error out]]''.
* If the [[VI]] is a [[Method (object-oriented programming)|method]] in a [[Class (object-oriented programming)|class]], use the top corners as the class object input and output.

=== Require by Default ===
* Turn the flag in the [[Options dialog]] on which will require all inputs by default, except the ''error in''. This makes it so inputs to [[SubVI]]s don't get accidentally forgotten.

== History ==

{| class="wikitable"
! Version
! Change(s)
|-
|[[File:LV8-2013.png|frameless|border|64x64px|LabVIEW 2011|link=LabVIEW 2011]]
|In [[LabVIEW 2011]] the Connector Pane was changed to always be visible on the [[Front Panel]] window next to the [[VI Icon]]. [[LabVIEW 2010]] and earlier only the Connector Pane or the [[VI Icon]] was visible at a time and they were toggled between via a right-click menu ('''Show Connector''' or '''Show Icon''').

Also, previously to [[LabVIEW 2011]], when creating a SubVI from a selection, the SubVI would be created with a varying pattern with just the number of inputs or outputs needed. In [[LabVIEW 2011]] and later, the new SubVI will default to the 4x2x2x4 pattern, if the input/output count fits, and the errors will default to the bottom corners.
|}

== See Also ==
* [[Front Panel]]
* [[Block Diagram]]
* [[VI Icon]]

[[Category:Calling a VI]]
[[Category:Connector Pane]]

ProjectItem class/Get All Descendents method

2024-05-24T07:54:24Z

Thoric: Added a useful link to the list of valid Type strings.

{{VIServerMethod
| classid = 74
| methodid = 35B53810
| scope=basic
| dataname = Get All Descendents
| shortname = Get All Descendents
| longname = Get All Descendents
| datatypeimage = ProjectItem Refnum Array Indicator.png
| datatype = ProjectItem Refnum Array
| invokenodeimage = ProjectItem-Get All Descendents.png
| availableinrealtime = No
| availableinruntime = Yes (Read/Write)
| loadsbd = No
| loadsfp = No
| needsauthentication = No
| remoteallowed = Yes
| settablewhenrunning = No
|}}
{{TOCright}}
Recursively returns project items that appear under the referenced item in the project tree. For example, if you call this method on project library A that contains an inner project library B, the method returns items owned both by library A and library B.

For this method, the term descendents does not refer to children classes of the referenced project item.
==Parameters==
{| class="wikitable"
|-
! scope="column" style="text-align:Center;" | Data type
! scope="column" style="text-align:Left;" | Name
! scope="column" style="text-align:Left;" | Required
! scope="column" style="text-align:Left;" | Description
|-
! scope="row" style="text-align:Center;" | [[File:ProjectItem Refnum Array Indicator.png|frameless|border|ProjectItem Refnum Array|link=ProjectItem Refnum Array data type]]
| '''Get All Descendents'''
| Yes. Return value.
|
|-
! scope="row" style="text-align:Center;" | [[File:String.png|frameless|border|String|link=String data type]]
| '''Type'''
| No
| Specifies which kind of project items this method returns. For a list of valid Type strings see [[ProjectItem]].
|-
! scope="row" style="text-align:Center;" | [[File:Boolean.png|frameless|border|Boolean|link=Boolean data type]]
| '''ExcludeDependencies'''
| No
| Specifies whether to ignore items under the <code>Dependencies</code> folder if the referenced item is a project. If the referenced item is a target, this input specifies whether to exclude items under the target. If the referenced item is neither a project nor a target, this input has no effect on the output of this method.
|-
! scope="row" style="text-align:Center;" | [[File:Boolean.png|frameless|border|Boolean|link=Boolean data type]]
| '''ExcludeBuilds'''
| No
| If TRUE, does not return Build Specifications or any items under Build Specifications. The default is FALSE.
|-
! scope="row" style="text-align:Center;" | [[File:Boolean.png|frameless|border|Boolean|link=Boolean data type]]
| '''ExcludeTargets'''
| No
| If TRUE, does not return any targets or any items under targets. The default is FALSE.
|}

== Uses ==
The '''ProjectItem class/Get All Descendents method''' is used to get references to all of the children under the input referenced ProjectItem. The parameter ''Type'' is used to filter to just those that match that specific type. The [[ProjectItem class/Type String property]] can be used to get the ''Type'' of an item. A list of valid ''Type String'' values and their descriptions are listed on the [[ProjectItem]] page.

== History ==
{{ambox|text=History information is needed. What changes have occurred over previous versions?}}
{| class="wikitable"
! Version
! Change(s)
|-
|[[File:LV2018.png|frameless|border|64x64px|LabVIEW 2018|link=LabVIEW 2018]]
|More info to come.
|}
== See Also ==
{{ambox|text=Add links to internal wiki pages that would also help.}}

== External Links ==
{{ambox|text=Add links to external resources that would also help.}}

[[Category:VI Server Method]]

GDevCon

2020-01-08T00:24:34Z

Thoric:

[[Events]] : GDevCon 
 
[[File:Gdevconsmalllogo.jpg|frameless|right]]
'''GDevCon''' is an independent conference open to all graphical developers. It exists to help [[LabVIEW]] developers in teams learn and level up together, and it aims to help solve real problems encountered everyday by LabVIEW developers.

Designed as a series of events, GDevCon is focused on delivering world-class graphical programming material, from the community for the community. The conferences last several days and feature presentations by LabVIEW peers from around the world

The events do not mandate any level of certification, unlike the CLA Summits, enabling developers who don't choose to attain any formal accreditation to build connections to the LabVIEW community.

GDevCon is run by the [https://www.gdevcon.com/alliance GDevCon Alliance], a not-for-profit organisation that is independent from system vendors.
{{TOCright}}
{| class="wikitable"
|-
|[[File:GDevCon3GenevaSept.png|300px|frameless|left|link=GDevCon-3]]
| style="vertical-align:top;" |
== GDevCon #3 ==
[[GDevCon-3|GDevCon#3]] will be held in CERN, Geneva, on 8-9th September, the first event outside of the UK. To learn more visit the website [http://www.gdevcon.com GDevCon].
|-
|[[File:GDevCon2.png|300px|frameless|left|link=GDevCon-2]]
| style="vertical-align:top;" |
== GDevCon #2 ==
[[GDevCon-2|GDevCon#2]] was held in Birmingham, UK, on 21-22nd August at the inspiring [http://www.uniquevenuesbirmingham.com/ Unique Venues Birmingham (UVB)]. The event was headline sponsored by Dyson, with a strong emphasis on teams of developers attending together. This event was preceded by a sold-out workshop on Pragmatic Software Development.
|-
|[[File:GDevCon1.png|300px|frameless|left|link=GDevCon-1]]
| style="vertical-align:top;" |
== GDevCon #1 ==
[[GDevCon-1|GDevCon#1]] was held in Cambridge, UK, on 4-5th September 2018 at Murray Edwards College. The event was attended by over 140 developers, and actually had to be moved from their first venue, Girton College, to accommodate the higher than expected demand for tickets.

The success of GDevCon#1 proved that the LabVIEW community has matured to the point of running its own events in addition to NI's conferences.
|}
== History ==
The idea of GDevCon was born in the summer of 2017. In a discussion in June 2017 on the NI Champions forum, Steve Watts had jested about a new, community-driven LabVIEW event, and was backed up by Richard Thomas. The idea slowly evolved, with more and more people getting involved, who would finally form the GDevCon Alliance. The first company meeting of GDevCon Ltd. was held in London in November 2017. A [https://twitter.com/swatzyssdc/status/938159481799704577 tweet] on 5th of December 2017 by Steve Watts finally announced the project to the public.

== Other Resources ==
* [http://www.gdevcon.com GDevCon Website]
* [http://youtube.com/gdevcon GDevCon's YouTube channel]
* [https://www.flickr.com/photos/gdevcon/ GDevCon Flickr Album]
* [https://automatedenver.com/gdevcon-1-review/ Review of GdevCon #1]

[[Category:Conferences]]
[[Category:Events]]

File:GDevCon3GenevaSept.png

2020-01-08T00:24:02Z

Thoric:

GDevCon3 Logo

LabVIEW Wiki:Featured content

2018-11-22T15:52:41Z

Thoric:

[[GDevCon]] - the new Independent LabVIEW Conference

GDevCon

2018-11-22T15:50:20Z

Thoric: Created page with "right GDevCon is an independent organisation dedicated to creating a series of events that is all about world-class graphical programmi..."

[[File:Gdevconsmalllogo.jpg|frameless|right]]
GDevCon is an independent organisation dedicated to creating a series of events that is all about world-class graphical programming, organised by the community for the community.

Established in 2017, GDevCon held their first conference in Cambridge, UK, on 4-5th September 2018 at Murray Edwards College. The event was attended by over 140 developers, and actually had to be moved from their first venue, Girton College, to accommodate the higher than expected demand for tickets.

The event does not mandate any level of certification, unlike the CLA Summits, enabling access to developers who don't choose to attain any formal accreditation.

Based on the success of GDevCon#1, GDevCon intend to build on the format and organise additional conferences.

Visit the [http://www.gdevcon.com GDevCon] website to learn more about GDevCon and their future conferences.

File:Gdevconsmalllogo.jpg

2018-11-22T15:49:48Z

Thoric:

GDevCon Small Logo from website

Getting Started

2018-11-22T15:36:12Z

Thoric:

This page is intended to be a starting point and resource to help navigate all LabVIEW content on this Wiki and elsewhere.[[LabVIEW|General information about LabVIEW]]

*Basic Topics
**[[Training|Online Training]]
**[[LabVIEW_style_guide|LabVIEW Style Guide]]
**[[Community|Online Community]]
**[[Contributing_online|Contributing Online]]
**[[Finding_professional_help|Finding Professional Help]]
**[[Tips_and_tricks|Useful Tips and Tricks]]
**[[State_machine|State Machine Design Pattern]]
*Advanced Topics
**[[Object_oriented_software|Object Oriented Software]]
**[[Abstraction|Abstraction]]
**[[Actor_framework|Actor Framework]]
**[[Error_handling|Error Handling]]
**[[Source_code_control|Source Code Control]]
**[[SOLID_principals|SOLID Principals]]
**[[Unit_testing|Unit Testing]]
**[[VI_analyzer|VI Analyzer]]
**[[Virtual_machines|Virtual Machines]]
*Connecting With Other Developers
**[[User_groups|User Groups]]
**[[NI_week|NI Week]]
**[[GDevCon|GDevCon]]
**[[Summits|Summits]]
*[[LabVIEW_blogs|LabVIEW Blogs]]
*[[Online_videos|Online Videos]]
*[[Certifications|Certifications]]

<ul><li>[[data flow|Data Flow]]</li><li>[[LabVIEW tutorial|LabVIEW Tutorial]]</li><li>Hardware Basics</li></ul>

[[Category:Lists]]

LabVIEW configuration file/Block Diagram

2018-11-22T13:52:07Z

Thoric:

This is a list of LabVIEW ini File settings relating to Block Diagram behaviour.

{{TOCnestright}}

{{ labviewconfigurationkey
| keyname = allowDragDropFromFileDlg
| example = allowDragDropFromFileDlg=TRUE
| datatype = b
| description = Enables drag and drop functionality from the file dialog to the block diagram of a vi
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 8.5
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = This functionality existed in LV 5.0 -> LV 7.1, was removed in LV 8.x, and added back in as an ini setting in 8.5
}}
{{ labviewconfigurationkey
| keyname = autoWireMax
| example = autoWireMax=24
| datatype = i
| description = Maximum distance between nodes for autowiring to be active
| permitted_values = 1 to 232
| default = 16
| LV1 =6
| LV2 =7
| LV3 =8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = This setting is only effective if [[#enableAutoWire|enableAutoWire]] is set to TRUE
}}
{{ labviewconfigurationkey
| keyname = autoWireMin
| example = autoWireMin=8
| datatype = i
| description = Minimum distance between nodes for autowiring to be active
| permitted_values = 1 to 232
| default = 4
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = This setting is only effective if [[#enableAutoWire|enableAutoWire]] is set to TRUE
}}
{{ labviewconfigurationkey
| keyname = copyDeleteFPDCOFromFPTerm
| example = copyDeleteFPDCOFromFPTerm=TRUE
| datatype = b
| description = Delete front panel terminals from diagram
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = enableAutoWire
| example = enableAutoWire=FALSE
| datatype = b
| description = Enable Auto Wiring
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = FancyFPTerms
| example = FancyFPTerms=FALSE
| datatype = b
| description = Place front panel terminals as icons
| permitted_values = TRUE or FALSE
| default = (Depends on LV Version)
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = http://forums.lavag.org/FancyFPTerms-in-LabVIEWini-t725.html
}}
{{ labviewconfigurationkey
| keyname = funkyErrClustWire
| example = funkyErrClustWire=FALSE
| datatype = b
| description = Change Error Cluster wires color from the standard cluster pink to a more distinctive brown/green color
| permitted_values = TRUE or FALSE
| default = LabVIEW 5.1, 6.x, 7.x: FALSE, LabVIEW 8.x: TRUE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = inlineSubVIEnabled
| example = inlineSubVIEnabled=FALSE
| datatype = b
| description = Allows the context menu item "Inline SubVI" on any SubVI which inserts the code directly into the block diagram containing the SubVI.
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = maxUndoSteps
| example = maxUndoSteps=50
| datatype = i
| description = Maximum undo steps per VI
| permitted_values = 1 to 99
| default = 8
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showSubVIName
| example = showSubVIName=TRUE
| datatype = b
| description = Show subVI names when dropped
| 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 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showTipStringsOnTerms
| example = showTipStringsOnTerms=FALSE
| datatype = b
| description = Show tip-strips over terminals
| 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 = showWireDots
| example = showWireDots=TRUE
| datatype = b
| description = Show dots at wire junctions
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =7
| LV2 =8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showWireGuides
| example = showWireGuides=FALSE
| datatype = b
| description = Show dashed line while wiring
| 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 = structuresFadeToDiagramBeneath
| example = structuresFadeToDiagramBeneath=FALSE
| datatype = b
| description = Makes the diagram of structures semi-transparent so that you can see objects behind them.
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =6
| LV2 =7
| LV3 =8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = Enabling this setting will slow down the development environment on large Block Diagrams. Feature disabled in LabVIEW 2014 onwards.
}}
{{ labviewconfigurationkey
| keyname = transparentBDLabels
| example = transparentBDLabels=TRUE
| datatype = b
| description = Use transparent name labels
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =5
| LV2 =6
| LV3 =7
| LV4 =8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = UseNumbersForNewVIIcons
| example = UseNumbersForNewVIIcons=FALSE
| datatype = b
| description = Tells LabVIEW whether to automatically include a number (1-9) in the lower-right corner of each new VI's icon.
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 = 8.6
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes = This key replaces [[#UseNumbersForNewVIIconsInLibs|UseNumbersForNewVIIconsInLibs]] from LabVIEW 8.5.
}}
{{ labviewconfigurationkey
| keyname = UseNumbersForNewVIIconsInLibs
| example = UseNumbersForNewVIIconsInLibs=FALSE
| datatype = b
| description = Tells LabVIEW whether to automatically include a number (1-9) in the lower-right corner of each new VI's icon for VIs created inside libraries (.lvlib, .lvclass, .xctl, .lvsc, etc).
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 = 8.5
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes = This key was replaced by [[#UseNumbersForNewVIIcons|UseNumbersForNewVIIcons]] in LabVIEW 8.6.
}}
{{ labviewconfigurationkey
| keyname = viCaptionTipStrings
| example = viCaptionTipStrings=FALSE
| datatype = b
| description = Use control captions for subVI tip-strips
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =5
| LV2 =6
| LV3 =7
| LV4 =8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = SourceOnlyEnvironment
| example = SourceOnlyEnvironment=True
| datatype = b
| description = The option "Separate Compiled Code from Source" is turned on by default
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =10
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 =
| OS3 =
| OS4 =
| notes = Currently this causes "uncomfortably" slow load times when opening a large number of VIs which this option enabled. Reference, [https://decibel.ni.com/content/groups/large-labview-application-development/blog/2010/09 NI forums]
}}

[[Category:Configuration File|Block Diagram]]

LabVIEW configuration file/Debugging

2013-12-13T14:31:50Z

Thoric:

This is a list of LabVIEW ini File settings relating to Debugging.
{{TOCright}}
{{ labviewconfigurationkey
| keyname = showExePathInWindowTitle
| example = showExePathInWindowTitle=TRUE
| datatype = b
| description = It puts the full path of every vi in the title bar (as well as the path and version to the LabVIEW instance the vi belongs to).
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 8.x
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes =
}}
{{ labviewconfigurationkey
| keyname = prettyExecHilite
| example = prettyExecHilite=FALSE
| datatype =b
| description =Show data flow trace bubbles during execution highlighting
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}
{{ labviewconfigurationkey
| keyname = autoProbe
| example = autoProbe=FALSE
| datatype =b
| description =Show data values on wires during execution highlighting
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}
{{ labviewconfigurationkey
| keyname = showWarnings
| example = showWarnings=TRUE
| datatype =b
| description =Show warnings in error box
| 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 =u
| notes =None
}}
{{ labviewconfigurationkey
| keyname = massCompAll
| example = massCompAll=TRUE
| datatype =b
| description =Forces Mass Compile to compile every VI
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 8.6.1 onwards
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes = source: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Force-Recompile-option-in-Mass-Compile/idc-p/2662843#M26036
}}

[[Category:Configuration File|Debugging]]

[[Category:Configuration File|Debugging]]

Richard Thomas (LabVIEW Champion)

2012-09-26T15:50:42Z

Thoric:

NI Handle: Thoric

Home: Cambridge, England

Programming Languages: LabVIEW (incl. RT and FPGA)

Certification: Certified LabVIEW Architect

Used LabVIEW Since: 2000 (Version 6i)

Applications Areas:
Software consultancy providing solutions to most scientific and industrial software challenges.
Biography:

I've programmed in LabVIEW since version 6i as a post-grad student at Leicester University, where I used LabVIEW to acquire and analyse data from a large scale laminar wind tunnel. I expanded my experience further when I took up a post-doc position at the Turbomachinery Group of the Engineering Department at Cambridge University, where LabVIEW is used extensively for hardware control and instrumentation acquisition and data analysis.

I currently work as a Senior Systems Engineer at Product Technology Partners, also based in Cambridge, UK. As a software consultancy we provide solutions to almost any scientific and industrial control challenge. I'm a hugely enthusiastic LabVIEW programmer, and enjoy pushing LabVIEW and NI hardware to their limits.

I host the Cambridge LabVIEW Users Group, one of only two user groups here in the UK, and frequently present material on a wide range of topics, with my favorites being Object Oriented programming and User Interface design.

Personally, when I'm not working with LabVIEW, I'm often finding things to break so that I can fix them (I'm an aspirational DIYer), and annoying the local townsfolk every Monday night ringing the church bells as a student campanologist.

User Groups:
I host and regularly present atthe Cambridge LabVIEW User Group (CLUG). We gather three times a year in the Cambridge area. Visit our website if you are interested and want to come along (http://www.labviewcambridge.co.uk/). The site has its own forum pages and a downloads section that includes all our presentations and demonstration material.

www.labviewcambridge.co.uk
www.ptpart.co.uk

[[Category:LabVIEW Champions]]

Richard Thomas (LabVIEW Champion)

2012-09-26T15:50:11Z

Thoric:

Avatar: Thoric

Home: Cambridge, England

Programming Languages: LabVIEW (incl. RT and FPGA)

Certification: Certified LabVIEW Architect

Used LabVIEW Since: 2000 (Version 6i)

Applications Areas:
Software consultancy providing solutions to most scientific and industrial software challenges.
Biography:

I've programmed in LabVIEW since version 6i as a post-grad student at Leicester University, where I used LabVIEW to acquire and analyse data from a large scale laminar wind tunnel. I expanded my experience further when I took up a post-doc position at the Turbomachinery Group of the Engineering Department at Cambridge University, where LabVIEW is used extensively for hardware control and instrumentation acquisition and data analysis.

I currently work as a Senior Systems Engineer at Product Technology Partners, also based in Cambridge, UK. As a software consultancy we provide solutions to almost any scientific and industrial control challenge. I'm a hugely enthusiastic LabVIEW programmer, and enjoy pushing LabVIEW and NI hardware to their limits.

I host the Cambridge LabVIEW Users Group, one of only two user groups here in the UK, and frequently present material on a wide range of topics, with my favorites being Object Oriented programming and User Interface design.

Personally, when I'm not working with LabVIEW, I'm often finding things to break so that I can fix them (I'm an aspirational DIYer), and annoying the local townsfolk every Monday night ringing the church bells as a student campanologist.

User Groups:
I host and regularly present atthe Cambridge LabVIEW User Group (CLUG). We gather three times a year in the Cambridge area. Visit our website if you are interested and want to come along (http://www.labviewcambridge.co.uk/). The site has its own forum pages and a downloads section that includes all our presentations and demonstration material.

www.labviewcambridge.co.uk
www.ptpart.co.uk

[[Category:LabVIEW Champions]]

Richard Thomas (LabVIEW Champion)

2012-09-26T15:49:56Z

Thoric:

Richard Thomas (LabVIEW Champion)

2012-09-26T15:49:36Z

Thoric: Created page with "{| class="wikitable"|-| Name: || Dr. Richard Thomas |-| NI Handle: || Thoric |-| Programming Languages: || LabVIEW (incl. RT, FPGA) |-| Certification: || Certified LabVIEW Archit..."

{| class="wikitable"|-| Name: || Dr. Richard Thomas |-| NI Handle: || Thoric |-| Programming Languages: || LabVIEW (incl. RT, FPGA) |-| Certification: || Certified LabVIEW Architect |-| Used LabVIEW Since: || 2000 (Version 6i) |}

Avatar: Thoric

Home: Cambridge, England

Programming Languages: LabVIEW (incl. RT and FPGA)

Certification: Certified LabVIEW Architect

Used LabVIEW Since: 2000 (Version 6i)

Applications Areas:
Software consultancy providing solutions to most scientific and industrial software challenges.
Biography:

I've programmed in LabVIEW since version 6i as a post-grad student at Leicester University, where I used LabVIEW to acquire and analyse data from a large scale laminar wind tunnel. I expanded my experience further when I took up a post-doc position at the Turbomachinery Group of the Engineering Department at Cambridge University, where LabVIEW is used extensively for hardware control and instrumentation acquisition and data analysis.

I currently work as a Senior Systems Engineer at Product Technology Partners, also based in Cambridge, UK. As a software consultancy we provide solutions to almost any scientific and industrial control challenge. I'm a hugely enthusiastic LabVIEW programmer, and enjoy pushing LabVIEW and NI hardware to their limits.

I host the Cambridge LabVIEW Users Group, one of only two user groups here in the UK, and frequently present material on a wide range of topics, with my favorites being Object Oriented programming and User Interface design.

Personally, when I'm not working with LabVIEW, I'm often finding things to break so that I can fix them (I'm an aspirational DIYer), and annoying the local townsfolk every Monday night ringing the church bells as a student campanologist.

User Groups:
I host and regularly present atthe Cambridge LabVIEW User Group (CLUG). We gather three times a year in the Cambridge area. Visit our website if you are interested and want to come along (http://www.labviewcambridge.co.uk/). The site has its own forum pages and a downloads section that includes all our presentations and demonstration material.

www.labviewcambridge.co.uk
www.ptpart.co.uk

[[Category:LabVIEW Champions]]

[[Category:LabVIEW Champions]]