LabVIEW Wiki - User contributions [en]

List of LabVIEW Champions

2025-04-13T20:30:05Z

Crelf: Updated my stage name

{{see also|LabVIEW Champion|LabVIEW Champions program FAQ}}
Complete List at NI.com: [https://forums.ni.com/t5/LabVIEW-Champions-Directory/tkb-p/3012 LabVIEW Champions]

{| class="wikitable sortable"
|-
! Name
! Tenure
! Home
|-
| [[Albert Geven (LabVIEW Champion)|Albert Geven]]
| 2005-Present
| Netherlands
|-
| [[Alessandro Ricco (LabVIEW Champion)|Alessandro Ricco]]
| 2005-Present
| Italy
|-
| [[André Manzolli (LabVIEW Champion)|André Manzolli]]
| 2005-Present
| Brazil
|-
| [[Ben Rayner (LabVIEW Champion)|Ben Rayner]]
| 2005-Present
| United States
|-
| [[Bill Meier (LabVIEW Champion)|Bill Meier]]
| 2010-Present
| United States
|-
| [[Bogdan Iwinski (LabVIEW Champion)|Bogdan Iwinski]]
| 2010-Present
| Poland
|-
| [[Brett Percy (LabVIEW Champion)|Brett Percy]]
| 2005-Present
| Australia
|-
| [[Bruce Ammons (LabVIEW Champion)|Bruce Ammons]]
| 2005-Present
| United States
|-
| [[Buddy Haun (LabVIEW Champion)|Buddy Haun]]
| 2008-Present
| United States
|-
| [[Charles Ghommidh (LabVIEW Champion)|Charles Ghommidh]]
| 2005-Present
| France
|-
| [[Chris Cilino (LabVIEW Champion)|Chris Cilino]]
| 2017-Present
| United States
|-
| [[Chris Roebuck (LabVIEW Champion)|Chris Roebuck]]
| 2013-Present
| United Kingdom
|-
| [[Christian Altenbach (LabVIEW Champion)|Christian Altenbach]]
| 2005-Present
| United States
|-
| [[Christian Butcher (LabVIEW Champion)|Christian Butcher]]
| 2021-Present
| Japan
|-
| [[Christophe Salzmann (LabVIEW Champion)|Christophe Salzmann]]
| 2010-Present
| United States
|-
| [[Christopher G. Relf (LabVIEW Champion)|Chris Relf]]
| 2005-Present
| United States
|-
| [[Cyril Gambini (LabVIEW Champion)|Cyril Gambini]]
| 2023-Present
| Canada
|-
| [[Dany Allard (LabVIEW Champion)|Dany Allard]]
| 2013-Present
| Canada
|-
| [[Darin Kinion (LabVIEW Champion)|Darin Kinion]]
| 2012-Present
| United States
|-
| [[David Thomson (LabVIEW Champion)|David Thomson]]
| 2005-Present
| United States
|-
| [[Dennis Knutson (LabVIEW Champion)|Dennis Knutson]]
| 2005-Present
| United States
|-
| [[Ed Dickens (LabVIEW Champion)|Ed Dickens]]
| 2005-Present
| United States
|-
| [[Ederson Ramalho (LabVIEW Champion)|Ederson Ramalho]]
| 2023-Present
| Brazil
|-
| [[Fabiola De la Cueva (LabVIEW Champion)|Fabiola De la Cueva]]
| 2012-Present
| United States
|-
| [[Felipe Pinheiro Silva (LabVIEW Champion)|Felipe Pinheiro Silva]]
| 2021-Present
| Brazil
|-
| [[Francois Normandin (LabVIEW Champion)|Francois Normandin]]
| 2019-Present
| Canada
|-
| [[Gaurav Kulkarni (LabVIEW Champion)|Gaurav Kulkarni]]
| 2013-Present
| India
|-
| [[Jeff Bohrer (LabVIEW Champion)|Jeff Bohrer]]
| 2012-Present
| United States
|-
| [[Jim Kring (LabVIEW Champion)|Jim Kring]]
| 2005-Present
| United States
|-
| [[Joe Hoskins (LabVIEW Champion)|Joe Hoskins]]
| 2010-Present
| United States
|-
| [[Joerg Hampel (LabVIEW Champion)|Joerg Hampel]]
| 2018-Present
| Austria
|-
| [[Jonathon Green (LabVIEW Champion)|Jonathon Green]]
| 2012-Present
| Australia
|-
| [[Justin Goeres (LabVIEW Champion)|Justin Goeres]]
| 2012-Present
| United States
|-
| [[Kabul Maharjan (LabVIEW Champion)|Kabul Maharjan]]
| 2019-Present
| United Kingdom
|-
| [[Kevin Shirey (LabVIEW Champion)|Kevin Shirey]]
| 2022-Present
| United States
|-
| [[Leigh Christian (LabVIEW Champion)|Leigh Christian]]
| 2010-Present
| United States
|-
| [[Marcus Johnson (LabVIEW Champion)|Marcus Johnson]]
| 2013-Present
| Sweden
|-
| [[Mark Balla (LabVIEW Champion)|Mark Balla]]
| 2010-Present
| United States
|-
| [[Mark Ridgley (LabVIEW Champion)|Mark Ridgley]]
| 2013-Present
| United States
|-
| [[Mark Yedinak (LabVIEW Champion)|Mark Yedinak]]
| 2010-Present
| United States
|-
| [[Michael Aivaliotis (LabVIEW Champion)|Michael Aivaliotis]]
| 2005-Present
| Canada
|-
| [[Mike Porter (LabVIEW Champion)|Mike Porter]]
| 2008-Present
| United States
|-
| [[Mike Radziwon (LabVIEW Champion)|Mike Radziwon]]
| 2024-Present
| Denmark
|-
| [[Muthuraman Sudalaimuthu (LabVIEW Champion)|Muthuraman Sudalaimuthu]]
| 2013-Present
| India
|-
| [[Nancy Hollenback (LabVIEW Champion)|Nancy Hollenback]]
| 2008-2010<ref>In 2010, Nancy joined NI.</ref>
| United States
|-
| [[Navin Subramani (LabVIEW Champion)|Navin Subramani]]
| 2021-Present
| United States
|-
| [[Norm Kirchner (LabVIEW Champion)|Norm Kirchner]]
| 2008-2008<ref>Months after becoming a Champion, Norm joined NI.</ref>
| United States
|-
| [[Quentin "Q" Alldredge (LabVIEW Champion)|Quentin "Q" Alldredge]]
| 2018-Present
| United States
|-
| [[Parag Deshpande (LabVIEW Champion)|Parag Deshpande]]
| 2012-Present
| India
|-
| [[Pavan Bathla (LabVIEW Champion)|Pavan Bathla]]
| 2007-Present
| United States
|-
| [[Piotr Maj (LabVIEW Champion)|Piotr Maj]]
| 2012-Present
| Poland
|-
| [[Putnam W. Monroe Jr. (LabVIEW Champion)|Putnam W. Monroe Jr.]]
| 2005-Present
| United States
|-
| [[Ray Robichaud (LabVIEW Champion)|Ray Robichaud]]
| 2005-Present
| Canada
|-
| [[Richard Sorrells (LabVIEW Champion)|Richard Sorrells]]
| 2013-Present
| United States
|-
| [[Rick Beauchaine (LabVIEW Champion)|Rick Beauchaine]]
| 2005-Present
| United States
|-
| [[Richard Thomas (LabVIEW Champion)|Richard Thomas]]
| 2012-Present
| England
|-
| [[Roger Isaksson (LabVIEW Champion)|Roger Isaksson]]
| 2013-Present
| Sweden
|-
| [[Rolf Kalbermatter (LabVIEW Champion)|Rolf Kalbermatter]]
| 2010-Present
| Netherlands
|-
| [[Sam Roundy (LabVIEW Champion)|Sam Roundy]]
| 2019-Present
| United States
|-
| [[Samuel James (LabVIEW Champion)|Samuel James]]
| 2012-Present
| India
|-
| [[Samuel Taggart (LabVIEW Champion)|Samuel Taggart]]
| 2018-Present
| United States
|-
| [[Saverio Mercurio (LabVIEW Champion)|Saverio Mercurio]]
| 2010-Present
| United States
|-
| [[Scott Hannahs (LabVIEW Champion)|Scott Hannahs]]
| 2005-Present
| United States
|-
| [[Shane O'Neill (LabVIEW Champion)|Shane O'Neill]]
| 2010-Present
| Switzerland
|-
| [[Steve Watts (LabVIEW Champion)|Steve Watts]]
| 2013-Present
| United Kingdom
|-
| [[Tim Robinson (LabVIEW Champion)|Tim Robinson]]
| 2013-Present
| United States
|-
| [[Tomi Maila (LabVIEW Champion)|Tomi Maila]]
| 2007-Present
| Finland
|-
| [[Tom McQuillan (LabVIEW Champion)|Tom McQuillan]]
| 2021-Present
| United Kingdom
|-
| [[Urs Lauterburg (LabVIEW Champion)|Urs Lauterburg]]
| 2005-Present
| Switzerland
|-
| [[Yair Neeman (LabVIEW Champion)|Yair Neeman]]
| 2007-Present
| Israel
|-
| [[Zbigniew Sobków (LabVIEW Champion)|Zbigniew Sobków]]
| 2005-Present
| Poland
|}

==References==
{{reflist}}

[[Category:Lists]]
[[Category:LabVIEW Champions]]

Christopher G. Relf (LabVIEW Champion)

2025-04-13T20:28:44Z

Crelf: /* Biography: man, that thing was stale... */

{{infobox
|category=person
|name=Chris Relf
|person-citizenship=Sothern California, USA
|person-title=champion
|person-certification=cla
|person-certification2=ctd
|person-first-labview-version=3.0
|person-application-area=
|person-application-area2=
|person-application-area3=
|person-application-area4=
|person-application-area5=
|person-application-area6=
|person-application-area7=
|person-certification3=cpi}}

== Biography: ==

Chris Relf is a founding [https://forums.ni.com/t5/LabVIEW-Champions/ct-p/7029 LabVIEW Champion], Director of Test at [https://www.virgingalactic.com/ Virgin Galactic] and author of "[http://www.amazon.com/Image-Acquisition-Processing-LabVIEW/dp/0849314801/ref=sr_1_1?ie=UTF8&s=books&qid=1240687027&sr=8-1 Image Acquisition and Processing with LabVIEW]" ([https://www.routledge.com/ Routledge Press]). Chris' industrial experience includes roles as the Director of Test at [https://en.wikipedia.org/wiki/Tyvak Tyvak/Terran Orbital], Director of Test and System Integration at [https://en.wikipedia.org/wiki/Virgin_Orbit Virgin Orbit], the Development Manager for [https://www.nvsi.com.au/pages/home.htm Neo Vista System Integrators], an Automation Scientist at the Division of Telecommunications and Industrial Physics of the Australian [http://www.csiro.au/ Commonweath Scientific and Industrial Research Organisation] (CSIRO), a Process Software Engineer [http://www.jdsu.com JDS Uniphase] and a freelance technical journalist for [http://www.acp.com.au/ Australian Consolidated Press].

=== Books: ===

*[http://www.amazon.com/exec/obidos/ASIN/0849314801/nationalinstrume Image Acquisition and Processing with LabVIEW (CRC Press)]
*[http://www.amazon.com/exec/obidos/ASIN/0849315867/nationalinstrume The Engineering Handbook 2nd &3rd Editions (CRC Press)]

=== Discussion Groups: ===

LAVA, Open-G, NI Discussion Forums

=== Websites: ===

*[https://crelf.com crelf.com]

=== Articles ===

#"NeoLOG - Datalogging with LabVIEW Plug-ins" - 2005 NI-Week Case Study - Relf C. G.
#"Australian Square Kilometer Array Site Testing" - 2005 NI-Week Case Study - Relf C. G., Raynal L.
#"Athlete Psychology Testing System" - 2005 NI-Week Case Study - Relf C. G.
#"RF Compliance Test System" - 2005 NI-Week Case Study - Relf C. G., Bowyer G. K.
#"Wheat Grain Crush Curve Analysis System" - 2003 NI-Week Case Study - Bowyer G. K., Relf C. G.
#"Custom System Integration and Commercial Off-The-Shelf Products" - 2005 Information Circular
#"TEDS - Are You Ready?" - What's New in Process Technology
#"PACs versus PLCs - What are the Real Differences?" - What's New in Process Technology
#"Data Validity - Are Your Numbers Legit?" - What's New in Process Technology
#"Automated Object Inspection - Finally a Mature Technology" - What's New in Process Technology
#"50 Ton Load Cell Testing System" - 2004 NI-Week Case Study - Raynal L., Granger W., Relf C. G.
#"Printed Circuit Board (PCB) Automated Inspection System" - 2004 NI-Week Case Study - Relf C. G.
#"CAMS - Cable Analysis Measurement System" - 2004 NI-Week Case Study - Relf C. G.
#"Rail Line Scan - Overhead Line Alignment Measurement" - 2004 NI-Week Case Study - Relf C. G.
#"Laboratory Subject Monitoring and Stimuli Delivery System" - 2004 NI-Week Case Study - Bowyer G. K., Relf C. G.
#"Alphachron™ He Extraction/Measurement Instrument" - 2004 NI-Week Case Study - Raynal L., Relf C. G., McInnes B.
#"LabVIEW Software Engineering" - 2004 The Engineering Handbook (2nd Ed.)
#"Environmental Chamber Monitoring and Control" - 2003 NI-Week Case Study - Granger L., Dick R., Relf C. G.
#"LabVIEW Automates Eccentricity Measurement in an Industrial Production Line" - 2002 NI-Week Case Study - Relf C. G.
#“Automated Object Inspection – Finally a Mature Technology” - What's New in Process Technology
#“Automated Object Inspection – Front-End Components” - What's New in Process Technology
#“Automated Object Inspection – Shedding a Little Light on the Subject” - What's New in Process Technology
#“Feedback to Better Control your Processes” - What's New in Process Technology
#“Closed Loop Control – Common Models” - What's New in Process Technology
#“Industrial Automobile Networks – Driving the Data” - What's New in Process Technology
#“Deterministic Data Acquisition and Control with a Real-Time Operating System (Part 1)” - What's New in Process Technology
#“Deterministic Data Acquisition and Control with a Real-Time Operating System (Part 2)” - What's New in Process Technology

=== User Groups: ===

[[OpenG]] User Group, LabVIEW Advanced Virtual Architects ([[LAVA]]) User Group.

==See also==
*[[List of LabVIEW Champions]]
*[[LabVIEW Champions]]

LabVIEW 2023 Q3

2024-02-01T23:43:11Z

Crelf:

{{prevnext|LabVIEW 2023 Q1|LabVIEW Versions|LabVIEW 2024 Q1}}
{{LabVIEW Version
|version=LabVIEW 2023 Q3
|logo=File:LV2023.png
|release=24.07.2023
|change_0=Block diagram zoom
|change_1=Different animation speeds
|change_2=Change label to data type
|change_3=Create controls while wiring
|change_4=Apple silicon support}}

LabVIEW 2023 Q3 was released on July 24th, 2023.<ref name="labview-download"/>

==Added==
* Added [[Block Diagram]] zoom (from 25% to 250%).<ref name="diagram-zoom"/>
* Added [[JKI Dragon]] support.
* Added the ability to create [[control]]s, [[indicator]]s, or [[constant]]s while wiring.<ref name="create-control-indicator"/>
* Added a [[Quick Change]] menu to change the content of a [[free label]] to a [[Simple data type|simple]] or [[Array data type|array]] data type.<ref name="change-to-object"/>
* Added a [[Quick Change]] palette to wrap the content under a selection rectangle in a [[structure]], or extract it into a [[SubVI]].<ref name="wrap-in-structure"/>
* Added support for [[Find All Instances]] when a VI is running.<ref name="find-all-instances"/>
* Added different animation speeds for [[execution highlighting]]:<ref name="execution-highlighting"/>
** Slow
** Medium (default)
** Fast
** Very Fast
* Added [[corner mark]]s to toolbar buttons that provide additional options:<ref name="corner-markers"/>
** [[Execution highlighting|Highlight Execution]]
** [[Debugging Basics|Step Out]]
* Added support for [[wikipedia:Apple silicon|Apple silicon]].<ref name="apple-silicon"/>
* New configuration file tokens
** <code>EnableEmacsTextEditingShortcuts</code> Enables test editing bindings for macOS and Linux. Default: True.<ref name="EnableEmacsTextEditingShortcuts"/>
** <code>DoubleClickWhenWiringCreation</code> Enables double-click to finish wiring and create control/indicator/constant. Default: True.<ref name="DoubleClickWhenWiringCreation"/>

==Changed==
* Changed how the build cache for [[Application]]s, [[Packed Project Library|Packed Project Libraries]] and [[Source Distribution]]s works, so that subsequent builds are much faster.<ref name="build-caching"/>
* Changed the visual feedback when hovering and branching wires.<ref name="wire-highlighting"/>
* Changed the hotkeys to modify the font size to <code>Ctrl</code>+<code><</code> (smaller) and <code>Ctrl</code>+<code>></code> (larger).<ref name="execution-highlighting"/>

==Removed==
Nothing.

==External links==
* [https://forums.ni.com/t5/LabVIEW/Announcing-LabVIEW-2023-Q3/td-p/4318494 Announcing LabVIEW 2023 Q3!]

==References==
<references>
<ref name="labview-download>[https://www.ni.com/en-us/support/downloads/software-products/download.labview.html LabVIEW 2023 Q3]</ref>
<ref name="diagram-zoom">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Diagram-Zoom/td-p/4297781 New Feature: Diagram Zoom]</ref>
<ref name="execution-highlighting">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Multiple-Animation-Speeds-for-Execution-Highlighting/td-p/4297785 New Feature: Multiple Animation Speeds for Execution Highlighting]</ref>
<ref name="change-to-object">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Quick-Change-Label-to-Object/td-p/4298001 New Feature: Quick Change Label to Object]</ref>
<ref name="wrap-in-structure">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Quick-Change-Rectangular-Selection/td-p/4298007 New Feature: Quick Change Rectangular Selection]</ref>
<ref name="create-control-indicator">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Double-click-to-Finish-Wiring-and-Create-Control/td-p/4298009 New Feature: Double-click to Finish Wiring and Create Control/Indicator/Constant]</ref>
<ref name="find-all-instances">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Find-All-Instances-When-Running/td-p/4298073 New Feature: Find All Instances When Running]</ref>
<ref name="wire-highlighting">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-New-Visual-Feedback-When-Selecting-and-Branching/td-p/4298011 New Feature: New Visual Feedback When Selecting and Branching Wires]</ref>
<ref name="build-caching">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Performance-Improvements-to-Building-Applications/td-p/4298080 New Feature: Performance Improvements to Building Applications, Packed Project Libraries and Source Distributions]</ref>
<ref name="apple-silicon">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-LabVIEW-for-macOS-Supports-Apple-Silicon/td-p/4298013 New Feature: LabVIEW for macOS Supports Apple Silicon]</ref>
<ref name="corner-markers">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Multiple-Animation-Speeds-for-Execution-Highlighting/m-p/4299630/highlight/true#M56 Re: New Feature: Multiple Animation Speeds for Execution Highlighting]</ref>
<ref name="EnableEmacsTextEditingShortcuts">[https://forums.ni.com/t5/LabVIEW/Announcing-LabVIEW-2023-Q3/td-p/4318494#:~:text=Text%20Editing%20Shortcuts%20on%20macOS%20and%20Linux EnableEmacsTextEditingShortcuts]</ref>
<ref name="DoubleClickWhenWiringCreation">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Double-click-to-Finish-Wiring-and-Create-Control/m-p/4318913/highlight/true#M228 DoubleClickWhenWiringCreation]</ref>
</references>

[[Category:Added BD zoom clarification]]

History of GOOP

2014-05-15T19:14:52Z

Crelf: /* DataAct dqGOOP */

==V I Engineering VISTA Class Generator==
[[File:VISTAClassGenerator.png|thumb|VISTA Class Generator]]
Inspired by the implementation of the Config File VIs that shipped in vilib in LabVIEW 3.0, David Hoadley ([http://www.viengineering.com V I Engineering] Director of Engineering) and Stan Case (Senior Project Engineer) created a class generator that would dynamically create by-reference LabVIEW classes. 

The generator would prompt the user to name the class, and then create a control (for private member data) and methods, to be filled out by the user later. The generation of the class was by copying of an existing class template that shipped with the class generator, and a very early implementation of LabVIEW scripting to rename and recompile the new class.

The reference used to distinguish objects was a datalog file refnum, with a single-element enum inside it - the data value of the enum (the text in the 0th element) defined the actual datatype of the class, prohibiting cross-pollination of object types (LabVIEW would break wires that were connected between different class types). All code in the generated class, as well as the generator, was pure LabVIEW.
The VISTA Class Generator was bundled (along with other components of the VISTA product offerings) with the VIE LabVIEW Advanced Application Development Course. The course was later acquired by National Instruments, and forms the foundation of the existing LabVIEW Advanced Course.

The VISTA Class Generator was deprecated in 2000, and V I Engineering became the North American distributor and support center for Endevo GOOP and the GOOP Development Suite.

==Endevo GOOP and the GOOP Development Suite==
[[File:EndevoGDS.png|thumb|Endevo GOOP Development Toolkit]]
An excerpt from an OpenG discussion forum posting from Mattias Ericsson (Endevo project leader and main developer of the GOOP2, Wizard 2 and 3) to Jim Kring on: Tue 01 of Jul, 2003 
''The GOOP history began back in 1994 when Jörgen Jehander (one of the founders of Endevo) developed the first GOOP, actually taking advantage of his background as a C++ programmer and found a way of implementing OO in LabVIEW. This was a genuine LabVIEW implementation of the GOOP. There existed no Wizard back then. During 1994 and 1997 the GOOP went through many changes, especially the attribute synchronization and reference handling.'' 

''In 1997, a GOOP course, "LabVIEW System Design with GOOP" was held for the first time in Sweden and been held ever since and has also just recently started in the US.'' 

''In 1998-99 a cooperation began between Jörgen Jehander and Stepan Rhia from NI which started to developed the GOOP (the CIN based). The design was made both by Jörgen and Stepan, but it was Stepan who implemented both the CIN and the _goopsup.llb (included in LabVIEW 6 in vi.lib/platform). The reason why there is a CIN and not a LabVIEW implementation is that back then the performance was better with a CIN, but when LabVIEW 6 was launched (which has a much improved memory management) the benifits of using a CIN is gone. The GOOP Wizard 1.0, which might be download from ni.com, was developed in 1999 both by Jörgen and Stepan.'' 

''In 2002, Endevo launched a new GOOP Wizard 2, a new tool for creating and editing GOOP classes. This is not a new implementation of GOOP itself, but is only an improved Wizard with a lot of editing functionallity and also build-in icon generation. This Wizard is not distributed by NI, but may be bought from the Endevo homepage.'' 

''In 2003, a new GOOP, called GOOP2, is launched which has full support for inheritance (method and attribute inheritance, virtual methods and also static attributes) together with a new Wizard, the GOOP Wizard 3. This is sold as a new toolkit, GOOP Inheritance Toolkit. This new GOOP2 is a genuine LabVIEW implementation (no CIN, DLL or anything strange).'' 

The GOOP Development Suite was acquired by National Instruments in 2014, and is now a free [http://sine.ni.com/nips/cds/view/p/lang/en/nid/209038 download] from the LabVIEW Tools Network.

==OpenG OpenGOOP==
==SciWare GOOP Developer==
==DataAct dqGOOP==
[[File:DqGOOP.png|thumb|dqGOOP]]
As the name suggests, the dqGOOP design is based on a queue of a single element that encapsulates the private class data. Created in 2003 for LabVIEW 7, the architect concentrated on delivering a toolkit where the performance of the system was key. An excerpt from the dqGOOP website: 
''Most of the existing GOOP examples involve classes with relatively few objects that get created at the application initialization and destroyed at the end. What if you want to build an application applying OOP principals where there are hundreds or even thousands of objects and the design entails that one object may contain multiple other objects which in turn contain objects themselves?'' 

''I started to develop such an application and soon ran into the performance limitations of the existing GOOP frameworks... There was an offhanded comment on the Info-LabVIEW mailing list about how the queues in LabVIEW were improved in LabVIEW 7. Then I started to poke at the concept of using a queue as the data store for GOOP objects. Not only is the access fast, but queues have built in locking which means there is no need to create Semaphores or Occurrences. I used the new "Show Buffers..." tool and focused on creating the dqGOOP VIs with one priority...PERFORMANCE.'' 

dqGOOP is free and can be [http://www.dataact.com/dqGOOP.htm downloaded] from the DataAct website.

== See Also ==
{{Portal|GOOP}}

[[Category:GOOP]]

[[Category:GOOP]]

History of GOOP

2014-05-15T19:14:21Z

Crelf: /* DataAct dqGOOP */

==V I Engineering VISTA Class Generator==
[[File:VISTAClassGenerator.png|thumb|VISTA Class Generator]]
Inspired by the implementation of the Config File VIs that shipped in vilib in LabVIEW 3.0, David Hoadley ([http://www.viengineering.com V I Engineering] Director of Engineering) and Stan Case (Senior Project Engineer) created a class generator that would dynamically create by-reference LabVIEW classes. 

The generator would prompt the user to name the class, and then create a control (for private member data) and methods, to be filled out by the user later. The generation of the class was by copying of an existing class template that shipped with the class generator, and a very early implementation of LabVIEW scripting to rename and recompile the new class.

The reference used to distinguish objects was a datalog file refnum, with a single-element enum inside it - the data value of the enum (the text in the 0th element) defined the actual datatype of the class, prohibiting cross-pollination of object types (LabVIEW would break wires that were connected between different class types). All code in the generated class, as well as the generator, was pure LabVIEW.
The VISTA Class Generator was bundled (along with other components of the VISTA product offerings) with the VIE LabVIEW Advanced Application Development Course. The course was later acquired by National Instruments, and forms the foundation of the existing LabVIEW Advanced Course.

The VISTA Class Generator was deprecated in 2000, and V I Engineering became the North American distributor and support center for Endevo GOOP and the GOOP Development Suite.

==Endevo GOOP and the GOOP Development Suite==
[[File:EndevoGDS.png|thumb|Endevo GOOP Development Toolkit]]
An excerpt from an OpenG discussion forum posting from Mattias Ericsson (Endevo project leader and main developer of the GOOP2, Wizard 2 and 3) to Jim Kring on: Tue 01 of Jul, 2003 
''The GOOP history began back in 1994 when Jörgen Jehander (one of the founders of Endevo) developed the first GOOP, actually taking advantage of his background as a C++ programmer and found a way of implementing OO in LabVIEW. This was a genuine LabVIEW implementation of the GOOP. There existed no Wizard back then. During 1994 and 1997 the GOOP went through many changes, especially the attribute synchronization and reference handling.'' 

''In 1997, a GOOP course, "LabVIEW System Design with GOOP" was held for the first time in Sweden and been held ever since and has also just recently started in the US.'' 

''In 1998-99 a cooperation began between Jörgen Jehander and Stepan Rhia from NI which started to developed the GOOP (the CIN based). The design was made both by Jörgen and Stepan, but it was Stepan who implemented both the CIN and the _goopsup.llb (included in LabVIEW 6 in vi.lib/platform). The reason why there is a CIN and not a LabVIEW implementation is that back then the performance was better with a CIN, but when LabVIEW 6 was launched (which has a much improved memory management) the benifits of using a CIN is gone. The GOOP Wizard 1.0, which might be download from ni.com, was developed in 1999 both by Jörgen and Stepan.'' 

''In 2002, Endevo launched a new GOOP Wizard 2, a new tool for creating and editing GOOP classes. This is not a new implementation of GOOP itself, but is only an improved Wizard with a lot of editing functionallity and also build-in icon generation. This Wizard is not distributed by NI, but may be bought from the Endevo homepage.'' 

''In 2003, a new GOOP, called GOOP2, is launched which has full support for inheritance (method and attribute inheritance, virtual methods and also static attributes) together with a new Wizard, the GOOP Wizard 3. This is sold as a new toolkit, GOOP Inheritance Toolkit. This new GOOP2 is a genuine LabVIEW implementation (no CIN, DLL or anything strange).'' 

The GOOP Development Suite was acquired by National Instruments in 2014, and is now a free [http://sine.ni.com/nips/cds/view/p/lang/en/nid/209038 download] from the LabVIEW Tools Network.

==OpenG OpenGOOP==
==SciWare GOOP Developer==
==DataAct dqGOOP==
[[File:DqGOOP.png|thumb|dqGOOP]]
As the name suggests, the dqGOOP design is based on a queue of a single element that encapsulates the private class data. Created in 2003 for LabVIEW 7, the architect concentrated on delivering a toolkit where the performance of the system was key. An excerpt from the dqGOOP website: 
''Most of the existing GOOP examples involve classes with relatively few objects that get created at the application initialization and destroyed at the end. What if you want to build an application applying OOP principals where there are hundreds or even thousands of objects and the design entails that one object may contain multiple other objects which in turn contain objects themselves?'' 

''I started to develop such an application and soon ran into the performance limitations of the existing GOOP frameworks... There was an offhanded comment on the Info-LabVIEW mailing list about how the queues in LabVIEW were improved in LabVIEW 7. Then I started to poke at the concept of using a queue as the data store for GOOP objects. Not only is the access fast, but queues have built in locking which means there is no need to create Semaphores or Occurrences. I used the new "Show Buffers..." tool and focused on creating the dqGOOP VIs with one priority...PERFORMANCE.'' 

dqGOOP is free and can be http://www.dataact.com/dqGOOP.htm from the DataAct website.

== See Also ==
{{Portal|GOOP}}

[[Category:GOOP]]

[[Category:GOOP]]

File:DqGOOP.png

2014-05-15T19:13:46Z

Crelf: dqGOOP Screen Shot

dqGOOP Screen Shot

History of GOOP

2014-05-15T19:12:45Z

Crelf: /* Endevo GOOP and the GOOP Development Suite */

==V I Engineering VISTA Class Generator==
[[File:VISTAClassGenerator.png|thumb|VISTA Class Generator]]
Inspired by the implementation of the Config File VIs that shipped in vilib in LabVIEW 3.0, David Hoadley ([http://www.viengineering.com V I Engineering] Director of Engineering) and Stan Case (Senior Project Engineer) created a class generator that would dynamically create by-reference LabVIEW classes. 

The generator would prompt the user to name the class, and then create a control (for private member data) and methods, to be filled out by the user later. The generation of the class was by copying of an existing class template that shipped with the class generator, and a very early implementation of LabVIEW scripting to rename and recompile the new class.

The reference used to distinguish objects was a datalog file refnum, with a single-element enum inside it - the data value of the enum (the text in the 0th element) defined the actual datatype of the class, prohibiting cross-pollination of object types (LabVIEW would break wires that were connected between different class types). All code in the generated class, as well as the generator, was pure LabVIEW.
The VISTA Class Generator was bundled (along with other components of the VISTA product offerings) with the VIE LabVIEW Advanced Application Development Course. The course was later acquired by National Instruments, and forms the foundation of the existing LabVIEW Advanced Course.

The VISTA Class Generator was deprecated in 2000, and V I Engineering became the North American distributor and support center for Endevo GOOP and the GOOP Development Suite.

==Endevo GOOP and the GOOP Development Suite==
[[File:EndevoGDS.png|thumb|Endevo GOOP Development Toolkit]]
An excerpt from an OpenG discussion forum posting from Mattias Ericsson (Endevo project leader and main developer of the GOOP2, Wizard 2 and 3) to Jim Kring on: Tue 01 of Jul, 2003 
''The GOOP history began back in 1994 when Jörgen Jehander (one of the founders of Endevo) developed the first GOOP, actually taking advantage of his background as a C++ programmer and found a way of implementing OO in LabVIEW. This was a genuine LabVIEW implementation of the GOOP. There existed no Wizard back then. During 1994 and 1997 the GOOP went through many changes, especially the attribute synchronization and reference handling.'' 

''In 1997, a GOOP course, "LabVIEW System Design with GOOP" was held for the first time in Sweden and been held ever since and has also just recently started in the US.'' 

''In 1998-99 a cooperation began between Jörgen Jehander and Stepan Rhia from NI which started to developed the GOOP (the CIN based). The design was made both by Jörgen and Stepan, but it was Stepan who implemented both the CIN and the _goopsup.llb (included in LabVIEW 6 in vi.lib/platform). The reason why there is a CIN and not a LabVIEW implementation is that back then the performance was better with a CIN, but when LabVIEW 6 was launched (which has a much improved memory management) the benifits of using a CIN is gone. The GOOP Wizard 1.0, which might be download from ni.com, was developed in 1999 both by Jörgen and Stepan.'' 

''In 2002, Endevo launched a new GOOP Wizard 2, a new tool for creating and editing GOOP classes. This is not a new implementation of GOOP itself, but is only an improved Wizard with a lot of editing functionallity and also build-in icon generation. This Wizard is not distributed by NI, but may be bought from the Endevo homepage.'' 

''In 2003, a new GOOP, called GOOP2, is launched which has full support for inheritance (method and attribute inheritance, virtual methods and also static attributes) together with a new Wizard, the GOOP Wizard 3. This is sold as a new toolkit, GOOP Inheritance Toolkit. This new GOOP2 is a genuine LabVIEW implementation (no CIN, DLL or anything strange).'' 

The GOOP Development Suite was acquired by National Instruments in 2014, and is now a free [http://sine.ni.com/nips/cds/view/p/lang/en/nid/209038 download] from the LabVIEW Tools Network.

==OpenG OpenGOOP==
==SciWare GOOP Developer==
==DataAct dqGOOP==
As the name suggests, the dqGOOP design is based on a queue of a single element that encapsulates the private class data. Created in 2003 for LabVIEW 7, the architect concentrated on delivering a toolkit where the performance of the system was key. An excerpt from the dqGOOP website: 
''Most of the existing GOOP examples involve classes with relatively few objects that get created at the application initialization and destroyed at the end. What if you want to build an application applying OOP principals where there are hundreds or even thousands of objects and the design entails that one object may contain multiple other objects which in turn contain objects themselves?'' 

''I started to develop such an application and soon ran into the performance limitations of the existing GOOP frameworks... There was an offhanded comment on the Info-LabVIEW mailing list about how the queues in LabVIEW were improved in LabVIEW 7. Then I started to poke at the concept of using a queue as the data store for GOOP objects. Not only is the access fast, but queues have built in locking which means there is no need to create Semaphores or Occurrences. I used the new "Show Buffers..." tool and focused on creating the dqGOOP VIs with one priority...PERFORMANCE.'' 

dqGOOP is free and can be http://www.dataact.com/dqGOOP.htm from the DataAct website.

== See Also ==
{{Portal|GOOP}}

[[Category:GOOP]]

[[Category:GOOP]]

File:EndevoGDS.png

2014-05-15T19:09:23Z

Crelf: Endevo GOOP Development Toolkit Screenshot

Endevo GOOP Development Toolkit Screenshot

History of GOOP

2014-05-15T19:07:00Z

Crelf: /* V I Engineering VISTA Class Generator */

==V I Engineering VISTA Class Generator==
[[File:VISTAClassGenerator.png|thumb|VISTA Class Generator]]
Inspired by the implementation of the Config File VIs that shipped in vilib in LabVIEW 3.0, David Hoadley ([http://www.viengineering.com V I Engineering] Director of Engineering) and Stan Case (Senior Project Engineer) created a class generator that would dynamically create by-reference LabVIEW classes. 

The generator would prompt the user to name the class, and then create a control (for private member data) and methods, to be filled out by the user later. The generation of the class was by copying of an existing class template that shipped with the class generator, and a very early implementation of LabVIEW scripting to rename and recompile the new class.

The reference used to distinguish objects was a datalog file refnum, with a single-element enum inside it - the data value of the enum (the text in the 0th element) defined the actual datatype of the class, prohibiting cross-pollination of object types (LabVIEW would break wires that were connected between different class types). All code in the generated class, as well as the generator, was pure LabVIEW.
The VISTA Class Generator was bundled (along with other components of the VISTA product offerings) with the VIE LabVIEW Advanced Application Development Course. The course was later acquired by National Instruments, and forms the foundation of the existing LabVIEW Advanced Course.

The VISTA Class Generator was deprecated in 2000, and V I Engineering became the North American distributor and support center for Endevo GOOP and the GOOP Development Suite.

==Endevo GOOP and the GOOP Development Suite==
An excerpt from an OpenG discussion forum posting from Mattias Ericsson (Endevo project leader and main developer of the GOOP2, Wizard 2 and 3) to Jim Kring on: Tue 01 of Jul, 2003 
''The GOOP history began back in 1994 when Jörgen Jehander (one of the founders of Endevo) developed the first GOOP, actually taking advantage of his background as a C++ programmer and found a way of implementing OO in LabVIEW. This was a genuine LabVIEW implementation of the GOOP. There existed no Wizard back then. During 1994 and 1997 the GOOP went through many changes, especially the attribute synchronization and reference handling.'' 

''In 1997, a GOOP course, "LabVIEW System Design with GOOP" was held for the first time in Sweden and been held ever since and has also just recently started in the US.'' 

''In 1998-99 a cooperation began between Jörgen Jehander and Stepan Rhia from NI which started to developed the GOOP (the CIN based). The design was made both by Jörgen and Stepan, but it was Stepan who implemented both the CIN and the _goopsup.llb (included in LabVIEW 6 in vi.lib/platform). The reason why there is a CIN and not a LabVIEW implementation is that back then the performance was better with a CIN, but when LabVIEW 6 was launched (which has a much improved memory management) the benifits of using a CIN is gone. The GOOP Wizard 1.0, which might be download from ni.com, was developed in 1999 both by Jörgen and Stepan.'' 

''In 2002, Endevo launched a new GOOP Wizard 2, a new tool for creating and editing GOOP classes. This is not a new implementation of GOOP itself, but is only an improved Wizard with a lot of editing functionallity and also build-in icon generation. This Wizard is not distributed by NI, but may be bought from the Endevo homepage.'' 

''In 2003, a new GOOP, called GOOP2, is launched which has full support for inheritance (method and attribute inheritance, virtual methods and also static attributes) together with a new Wizard, the GOOP Wizard 3. This is sold as a new toolkit, GOOP Inheritance Toolkit. This new GOOP2 is a genuine LabVIEW implementation (no CIN, DLL or anything strange).'' 

The GOOP Development Suite was acquired by National Instruments in 2014, and is now a free [http://sine.ni.com/nips/cds/view/p/lang/en/nid/209038 download] from the LabVIEW Tools Network.

==OpenG OpenGOOP==
==SciWare GOOP Developer==
==DataAct dqGOOP==
As the name suggests, the dqGOOP design is based on a queue of a single element that encapsulates the private class data. Created in 2003 for LabVIEW 7, the architect concentrated on delivering a toolkit where the performance of the system was key. An excerpt from the dqGOOP website: 
''Most of the existing GOOP examples involve classes with relatively few objects that get created at the application initialization and destroyed at the end. What if you want to build an application applying OOP principals where there are hundreds or even thousands of objects and the design entails that one object may contain multiple other objects which in turn contain objects themselves?'' 

''I started to develop such an application and soon ran into the performance limitations of the existing GOOP frameworks... There was an offhanded comment on the Info-LabVIEW mailing list about how the queues in LabVIEW were improved in LabVIEW 7. Then I started to poke at the concept of using a queue as the data store for GOOP objects. Not only is the access fast, but queues have built in locking which means there is no need to create Semaphores or Occurrences. I used the new "Show Buffers..." tool and focused on creating the dqGOOP VIs with one priority...PERFORMANCE.'' 

dqGOOP is free and can be http://www.dataact.com/dqGOOP.htm from the DataAct website.

== See Also ==
{{Portal|GOOP}}

[[Category:GOOP]]

[[Category:GOOP]]

History of GOOP

2014-05-15T19:06:03Z

Crelf: /* V I Engineering VISTA Class Generator */

==V I Engineering VISTA Class Generator==
[[File:VISTAClassGenerator.png]]
Inspired by the implementation of the Config File VIs that shipped in vilib in LabVIEW 3.0, David Hoadley ([http://www.viengineering.com V I Engineering] Director of Engineering) and Stan Case (Senior Project Engineer) created a class generator that would dynamically create by-reference LabVIEW classes. 

The generator would prompt the user to name the class, and then create a control (for private member data) and methods, to be filled out by the user later. The generation of the class was by copying of an existing class template that shipped with the class generator, and a very early implementation of LabVIEW scripting to rename and recompile the new class.

The reference used to distinguish objects was a datalog file refnum, with a single-element enum inside it - the data value of the enum (the text in the 0th element) defined the actual datatype of the class, prohibiting cross-pollination of object types (LabVIEW would break wires that were connected between different class types). All code in the generated class, as well as the generator, was pure LabVIEW.
The VISTA Class Generator was bundled (along with other components of the VISTA product offerings) with the VIE LabVIEW Advanced Application Development Course. The course was later acquired by National Instruments, and forms the foundation of the existing LabVIEW Advanced Course.

The VISTA Class Generator was deprecated in 2000, and V I Engineering became the North American distributor and support center for Endevo GOOP and the GOOP Development Suite.

==Endevo GOOP and the GOOP Development Suite==
An excerpt from an OpenG discussion forum posting from Mattias Ericsson (Endevo project leader and main developer of the GOOP2, Wizard 2 and 3) to Jim Kring on: Tue 01 of Jul, 2003 
''The GOOP history began back in 1994 when Jörgen Jehander (one of the founders of Endevo) developed the first GOOP, actually taking advantage of his background as a C++ programmer and found a way of implementing OO in LabVIEW. This was a genuine LabVIEW implementation of the GOOP. There existed no Wizard back then. During 1994 and 1997 the GOOP went through many changes, especially the attribute synchronization and reference handling.'' 

''In 1997, a GOOP course, "LabVIEW System Design with GOOP" was held for the first time in Sweden and been held ever since and has also just recently started in the US.'' 

''In 1998-99 a cooperation began between Jörgen Jehander and Stepan Rhia from NI which started to developed the GOOP (the CIN based). The design was made both by Jörgen and Stepan, but it was Stepan who implemented both the CIN and the _goopsup.llb (included in LabVIEW 6 in vi.lib/platform). The reason why there is a CIN and not a LabVIEW implementation is that back then the performance was better with a CIN, but when LabVIEW 6 was launched (which has a much improved memory management) the benifits of using a CIN is gone. The GOOP Wizard 1.0, which might be download from ni.com, was developed in 1999 both by Jörgen and Stepan.'' 

''In 2002, Endevo launched a new GOOP Wizard 2, a new tool for creating and editing GOOP classes. This is not a new implementation of GOOP itself, but is only an improved Wizard with a lot of editing functionallity and also build-in icon generation. This Wizard is not distributed by NI, but may be bought from the Endevo homepage.'' 

''In 2003, a new GOOP, called GOOP2, is launched which has full support for inheritance (method and attribute inheritance, virtual methods and also static attributes) together with a new Wizard, the GOOP Wizard 3. This is sold as a new toolkit, GOOP Inheritance Toolkit. This new GOOP2 is a genuine LabVIEW implementation (no CIN, DLL or anything strange).'' 

The GOOP Development Suite was acquired by National Instruments in 2014, and is now a free [http://sine.ni.com/nips/cds/view/p/lang/en/nid/209038 download] from the LabVIEW Tools Network.

==OpenG OpenGOOP==
==SciWare GOOP Developer==
==DataAct dqGOOP==
As the name suggests, the dqGOOP design is based on a queue of a single element that encapsulates the private class data. Created in 2003 for LabVIEW 7, the architect concentrated on delivering a toolkit where the performance of the system was key. An excerpt from the dqGOOP website: 
''Most of the existing GOOP examples involve classes with relatively few objects that get created at the application initialization and destroyed at the end. What if you want to build an application applying OOP principals where there are hundreds or even thousands of objects and the design entails that one object may contain multiple other objects which in turn contain objects themselves?'' 

''I started to develop such an application and soon ran into the performance limitations of the existing GOOP frameworks... There was an offhanded comment on the Info-LabVIEW mailing list about how the queues in LabVIEW were improved in LabVIEW 7. Then I started to poke at the concept of using a queue as the data store for GOOP objects. Not only is the access fast, but queues have built in locking which means there is no need to create Semaphores or Occurrences. I used the new "Show Buffers..." tool and focused on creating the dqGOOP VIs with one priority...PERFORMANCE.'' 

dqGOOP is free and can be http://www.dataact.com/dqGOOP.htm from the DataAct website.

== See Also ==
{{Portal|GOOP}}

[[Category:GOOP]]

[[Category:GOOP]]

File:VISTAClassGenerator.png

2014-05-15T19:04:56Z

Crelf: VISTA Class Generator Screenshot

VISTA Class Generator Screenshot

History of GOOP

2014-05-14T17:49:40Z

Crelf: Added dqGOOP text

==V I Engineering VISTA Class Generator==
Inspired by the implementation of the Config File VIs that shipped in vilib in LabVIEW 3.0, David Hoadley ([http://www.viengineering.com V I Engineering] Director of Engineering) and Stan Case (Senior Project Engineer) created a class generator that would dynamically create by-reference LabVIEW classes. 

The generator would prompt the user to name the class, and then create a control (for private member data) and methods, to be filled out by the user later. The generation of the class was by copying of an existing class template that shipped with the class generator, and a very early implementation of LabVIEW scripting to rename and recompile the new class.

The reference used to distinguish objects was a datalog file refnum, with a single-element enum inside it - the data value of the enum (the text in the 0th element) defined the actual datatype of the class, prohibiting cross-pollination of object types (LabVIEW would break wires that were connected between different class types). All code in the generated class, as well as the generator, was pure LabVIEW.
The VISTA Class Generator was bundled (along with other components of the VISTA product offerings) with the VIE LabVIEW Advanced Application Development Course. The course was later acquired by National Instruments, and forms the foundation of the existing LabVIEW Advanced Course.

The VISTA Class Generator was deprecated in 2000, and V I Engineering became the North American distributor and support center for Endevo GOOP and the GOOP Development Suite.
==Endevo GOOP and the GOOP Development Suite==
An excerpt from an OpenG discussion forum posting from Mattias Ericsson (Endevo project leader and main developer of the GOOP2, Wizard 2 and 3) to Jim Kring on: Tue 01 of Jul, 2003 
''The GOOP history began back in 1994 when Jörgen Jehander (one of the founders of Endevo) developed the first GOOP, actually taking advantage of his background as a C++ programmer and found a way of implementing OO in LabVIEW. This was a genuine LabVIEW implementation of the GOOP. There existed no Wizard back then. During 1994 and 1997 the GOOP went through many changes, especially the attribute synchronization and reference handling.'' 

''In 1997, a GOOP course, "LabVIEW System Design with GOOP" was held for the first time in Sweden and been held ever since and has also just recently started in the US.'' 

''In 1998-99 a cooperation began between Jörgen Jehander and Stepan Rhia from NI which started to developed the GOOP (the CIN based). The design was made both by Jörgen and Stepan, but it was Stepan who implemented both the CIN and the _goopsup.llb (included in LabVIEW 6 in vi.lib/platform). The reason why there is a CIN and not a LabVIEW implementation is that back then the performance was better with a CIN, but when LabVIEW 6 was launched (which has a much improved memory management) the benifits of using a CIN is gone. The GOOP Wizard 1.0, which might be download from ni.com, was developed in 1999 both by Jörgen and Stepan.'' 

''In 2002, Endevo launched a new GOOP Wizard 2, a new tool for creating and editing GOOP classes. This is not a new implementation of GOOP itself, but is only an improved Wizard with a lot of editing functionallity and also build-in icon generation. This Wizard is not distributed by NI, but may be bought from the Endevo homepage.'' 

''In 2003, a new GOOP, called GOOP2, is launched which has full support for inheritance (method and attribute inheritance, virtual methods and also static attributes) together with a new Wizard, the GOOP Wizard 3. This is sold as a new toolkit, GOOP Inheritance Toolkit. This new GOOP2 is a genuine LabVIEW implementation (no CIN, DLL or anything strange).'' 

The GOOP Development Suite was acquired by National Instruments in 2014, and is now a free [http://sine.ni.com/nips/cds/view/p/lang/en/nid/209038 download] from the LabVIEW Tools Network.

==OpenG OpenGOOP==
==SciWare GOOP Developer==
==DataAct dqGOOP==
As the name suggests, the dqGOOP design is based on a queue of a single element that encapsulates the private class data. Created in 2003 for LabVIEW 7, the architect concentrated on delivering a toolkit where the performance of the system was key. An excerpt from the dqGOOP website: 
''Most of the existing GOOP examples involve classes with relatively few objects that get created at the application initialization and destroyed at the end. What if you want to build an application applying OOP principals where there are hundreds or even thousands of objects and the design entails that one object may contain multiple other objects which in turn contain objects themselves?'' 

''I started to develop such an application and soon ran into the performance limitations of the existing GOOP frameworks... There was an offhanded comment on the Info-LabVIEW mailing list about how the queues in LabVIEW were improved in LabVIEW 7. Then I started to poke at the concept of using a queue as the data store for GOOP objects. Not only is the access fast, but queues have built in locking which means there is no need to create Semaphores or Occurrences. I used the new "Show Buffers..." tool and focused on creating the dqGOOP VIs with one priority...PERFORMANCE.'' 

dqGOOP is free and can be http://www.dataact.com/dqGOOP.htm from the DataAct website.

== See Also ==
{{Portal|GOOP}}

[[Category:GOOP]]

[[Category:GOOP]]

History of GOOP

2014-05-14T17:35:20Z

Crelf: Added link to GDS download from ni.com

==V I Engineering VISTA Class Generator==
Inspired by the implementation of the Config File VIs that shipped in vilib in LabVIEW 3.0, David Hoadley ([http://www.viengineering.com V I Engineering] Director of Engineering) and Stan Case (Senior Project Engineer) created a class generator that would dynamically create by-reference LabVIEW classes. 

The generator would prompt the user to name the class, and then create a control (for private member data) and methods, to be filled out by the user later. The generation of the class was by copying of an existing class template that shipped with the class generator, and a very early implementation of LabVIEW scripting to rename and recompile the new class.

The reference used to distinguish objects was a datalog file refnum, with a single-element enum inside it - the data value of the enum (the text in the 0th element) defined the actual datatype of the class, prohibiting cross-pollination of object types (LabVIEW would break wires that were connected between different class types). All code in the generated class, as well as the generator, was pure LabVIEW.
The VISTA Class Generator was bundled (along with other components of the VISTA product offerings) with the VIE LabVIEW Advanced Application Development Course. The course was later acquired by National Instruments, and forms the foundation of the existing LabVIEW Advanced Course.

The VISTA Class Generator was deprecated in 2000, and V I Engineering became the North American distributor and support center for Endevo GOOP and the GOOP Development Suite.
==Endevo GOOP and the GOOP Development Suite==
An excerpt from an OpenG discussion forum posting from Mattias Ericsson (Endevo project leader and main developer of the GOOP2, Wizard 2 and 3) to Jim Kring on: Tue 01 of Jul, 2003 
''The GOOP history began back in 1994 when Jörgen Jehander (one of the founders of Endevo) developed the first GOOP, actually taking advantage of his background as a C++ programmer and found a way of implementing OO in LabVIEW. This was a genuine LabVIEW implementation of the GOOP. There existed no Wizard back then. During 1994 and 1997 the GOOP went through many changes, especially the attribute synchronization and reference handling.'' 

''In 1997, a GOOP course, "LabVIEW System Design with GOOP" was held for the first time in Sweden and been held ever since and has also just recently started in the US.'' 

''In 1998-99 a cooperation began between Jörgen Jehander and Stepan Rhia from NI which started to developed the GOOP (the CIN based). The design was made both by Jörgen and Stepan, but it was Stepan who implemented both the CIN and the _goopsup.llb (included in LabVIEW 6 in vi.lib/platform). The reason why there is a CIN and not a LabVIEW implementation is that back then the performance was better with a CIN, but when LabVIEW 6 was launched (which has a much improved memory management) the benifits of using a CIN is gone. The GOOP Wizard 1.0, which might be download from ni.com, was developed in 1999 both by Jörgen and Stepan.'' 

''In 2002, Endevo launched a new GOOP Wizard 2, a new tool for creating and editing GOOP classes. This is not a new implementation of GOOP itself, but is only an improved Wizard with a lot of editing functionallity and also build-in icon generation. This Wizard is not distributed by NI, but may be bought from the Endevo homepage.'' 

''In 2003, a new GOOP, called GOOP2, is launched which has full support for inheritance (method and attribute inheritance, virtual methods and also static attributes) together with a new Wizard, the GOOP Wizard 3. This is sold as a new toolkit, GOOP Inheritance Toolkit. This new GOOP2 is a genuine LabVIEW implementation (no CIN, DLL or anything strange).'' 

The GOOP Development Suite was acquired by National Instruments in 2014, and is now a free [http://sine.ni.com/nips/cds/view/p/lang/en/nid/209038 download] from the LabVIEW Tools Network.

==OpenG OpenGOOP==
==SciWare GOOP Developer==
==DataAct dqGOOP==
== See Also ==
{{Portal|GOOP}}

[[Category:GOOP]]

[[Category:GOOP]]

History of GOOP

2014-05-14T17:33:32Z

Crelf: Added VISTA Class Generator text

==V I Engineering VISTA Class Generator==
Inspired by the implementation of the Config File VIs that shipped in vilib in LabVIEW 3.0, David Hoadley ([http://www.viengineering.com V I Engineering] Director of Engineering) and Stan Case (Senior Project Engineer) created a class generator that would dynamically create by-reference LabVIEW classes. 

The generator would prompt the user to name the class, and then create a control (for private member data) and methods, to be filled out by the user later. The generation of the class was by copying of an existing class template that shipped with the class generator, and a very early implementation of LabVIEW scripting to rename and recompile the new class.

The reference used to distinguish objects was a datalog file refnum, with a single-element enum inside it - the data value of the enum (the text in the 0th element) defined the actual datatype of the class, prohibiting cross-pollination of object types (LabVIEW would break wires that were connected between different class types). All code in the generated class, as well as the generator, was pure LabVIEW.
The VISTA Class Generator was bundled (along with other components of the VISTA product offerings) with the VIE LabVIEW Advanced Application Development Course. The course was later acquired by National Instruments, and forms the foundation of the existing LabVIEW Advanced Course.

The VISTA Class Generator was deprecated in 2000, and V I Engineering became the North American distributor and support center for Endevo GOOP and the GOOP Development Suite.
==Endevo GOOP and the GOOP Development Suite==
An excerpt from an OpenG discussion forum posting from Mattias Ericsson (Endevo project leader and main developer of the GOOP2, Wizard 2 and 3) to Jim Kring on: Tue 01 of Jul, 2003 
''The GOOP history began back in 1994 when Jörgen Jehander (one of the founders of Endevo) developed the first GOOP, actually taking advantage of his background as a C++ programmer and found a way of implementing OO in LabVIEW. This was a genuine LabVIEW implementation of the GOOP. There existed no Wizard back then. During 1994 and 1997 the GOOP went through many changes, especially the attribute synchronization and reference handling.'' 

''In 1997, a GOOP course, "LabVIEW System Design with GOOP" was held for the first time in Sweden and been held ever since and has also just recently started in the US.'' 

''In 1998-99 a cooperation began between Jörgen Jehander and Stepan Rhia from NI which started to developed the GOOP (the CIN based). The design was made both by Jörgen and Stepan, but it was Stepan who implemented both the CIN and the _goopsup.llb (included in LabVIEW 6 in vi.lib/platform). The reason why there is a CIN and not a LabVIEW implementation is that back then the performance was better with a CIN, but when LabVIEW 6 was launched (which has a much improved memory management) the benifits of using a CIN is gone. The GOOP Wizard 1.0, which might be download from ni.com, was developed in 1999 both by Jörgen and Stepan.'' 

''In 2002, Endevo launched a new GOOP Wizard 2, a new tool for creating and editing GOOP classes. This is not a new implementation of GOOP itself, but is only an improved Wizard with a lot of editing functionallity and also build-in icon generation. This Wizard is not distributed by NI, but may be bought from the Endevo homepage.'' 

''In 2003, a new GOOP, called GOOP2, is launched which has full support for inheritance (method and attribute inheritance, virtual methods and also static attributes) together with a new Wizard, the GOOP Wizard 3. This is sold as a new toolkit, GOOP Inheritance Toolkit. This new GOOP2 is a genuine LabVIEW implementation (no CIN, DLL or anything strange).'' 
==OpenG OpenGOOP==
==SciWare GOOP Developer==
==DataAct dqGOOP==
== See Also ==
{{Portal|GOOP}}

[[Category:GOOP]]

[[Category:GOOP]]

History of GOOP

2014-05-14T17:20:14Z

Crelf: Reformatted, added headings for other GOOP implementations

==V I Engineering VISTA Class Generator==

==Endevo GOOP and the GOOP Development Suite==
An excerpt from an OpenG discussion forum posting from Mattias Ericsson (Endevo project leader and main developer of the GOOP2, Wizard 2 and 3) to Jim Kring on: Tue 01 of Jul, 2003 
''The GOOP history began back in 1994 when Jörgen Jehander (one of the founders of Endevo) developed the first GOOP, actually taking advantage of his background as a C++ programmer and found a way of implementing OO in LabVIEW. This was a genuine LabVIEW implementation of the GOOP. There existed no Wizard back then. During 1994 and 1997 the GOOP went through many changes, especially the attribute synchronization and reference handling.'' 

''In 1997, a GOOP course, "LabVIEW System Design with GOOP" was held for the first time in Sweden and been held ever since and has also just recently started in the US.'' 

''In 1998-99 a cooperation began between Jörgen Jehander and Stepan Rhia from NI which started to developed the GOOP (the CIN based). The design was made both by Jörgen and Stepan, but it was Stepan who implemented both the CIN and the _goopsup.llb (included in LabVIEW 6 in vi.lib/platform). The reason why there is a CIN and not a LabVIEW implementation is that back then the performance was better with a CIN, but when LabVIEW 6 was launched (which has a much improved memory management) the benifits of using a CIN is gone. The GOOP Wizard 1.0, which might be download from ni.com, was developed in 1999 both by Jörgen and Stepan.'' 

''In 2002, Endevo launched a new GOOP Wizard 2, a new tool for creating and editing GOOP classes. This is not a new implementation of GOOP itself, but is only an improved Wizard with a lot of editing functionallity and also build-in icon generation. This Wizard is not distributed by NI, but may be bought from the Endevo homepage.'' 

''In 2003, a new GOOP, called GOOP2, is launched which has full support for inheritance (method and attribute inheritance, virtual methods and also static attributes) together with a new Wizard, the GOOP Wizard 3. This is sold as a new toolkit, GOOP Inheritance Toolkit. This new GOOP2 is a genuine LabVIEW implementation (no CIN, DLL or anything strange).'' 
==OpenG OpenGOOP==
==SciWare GOOP Developer==
==DataAct dqGOOP==
== See Also ==
{{Portal|GOOP}}

[[Category:GOOP]]

Graphical Object-Oriented Programming

2014-05-14T16:58:56Z

Crelf:

This is the Portal for GOOP and LabVOOP.

GOOP stands for "Graphical Object-Oriented Programming."
LabVOOP stands for "LabVIEW Object-Oriented Programming."

GOOP is a term used to refer to the various OOP toolkits from V I Engineering, Endevo/NI, SciWare and OpenG. These toolkits were written in G.

LabVOOP refers to the native LabVIEW classes that first appeared in LV8.2.

The toolkits were not obsoleted by the native implementation. All of the toolkits use a reference model for passing objects on the block diagram, similar to File refnums or Queue refnums in LabVIEW. The native classes pass by value, similar to clusters and arrays. The two mechanisms are complementary, not exclusionary, and there may be times when both approaches are used in the same LV program.

==Pages Here:==
*[[GOOP - Graphical Object Oriented Programming]]
*[[History of GOOP]]
*[[LVOOP|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]]
*[[LVOOP Frequently Asked Questions]]

[[Category:GOOP]]

Forum Guidelines

2012-10-10T19:04:59Z

Crelf: /* Introduction */

__NOTOC__
{| align="right" border="0"
|__TOC__
|-
|}
== Introduction ==

'''These rules and guidelines apply to the discussion threads associated with LabVIEW Wiki articles.''' For Guidelines pertaining to other sites in the LAVA family see:

*[[LabVIEW Wiki:Policies and guidelines|LabVIEW Wiki Policies and Guidelines]]
*[[Help:Contents|Complete LabVIEW Wiki Help, FAQ and Guidelines]]
*[http://lavag.org/index.php?app=forums&module=extras&section=boardrules LAVA Forums Guidelines]
*[http://forums.lavag.org/Code-Repository-Discussions-f62.html Code Repository Information and Procedure]

The LabVIEW Wiki is managed and maintained by dedicated LabVIEW enthusiasts like yourself. We are volunteers committed to the development of an open and unbiased exchange of ideas on intermediate to advanced topics in LabVIEW. The document that follows covers key areas of the Forums and should answer most of your questions regarding features, proper usage and etiquette.

== Finding information ==

'''Use Search.''' Your question has probably already been answered. Before posting a LabVIEW question we recommend that you try checking the [[Portal:LabVIEW FAQ|LabVIEW FAQ]] and if your question is still not answered, [http://forums.lavag.org/labviewsearch.html Search the Forums]. A link for searching the Forums can be found in the top header banner at the top right of all pages in the Forums.

== Contributing and posting in the forums ==

*'''Use images'''. Images are the best way to convey the problem you are having. In LabVIEW this is more important because of the graphical nature of the language. You cannot include text code like you would in C++ or other languages. Please check our [http://forums.lavag.org/How-to-Insert-Images-in-your-Posts-t771.html Guide] for how to post images.
*'''Upload example code'''. We love that here. Please upload your code that you are having problems with. You can include all your code into a single [[llb]] or just include all vi's into a *.zip file format. If certain files are missing then it will be more difficult for others to help you with your problem. You will be surprised how many people are willing to re-write your code and make suggestions for you. This can only happen with functional code. Are you uploading code in response to a question? If so then please respect the recipient's LabVIEW version. If you can, perform a save to previous version on your code so they can open it up in their LabVIEW development environment. If the code is very simple and is contained on one diagram then you might want to consider posting an image of the solution instead.
*'''Post in the right Forum'''. Choose a Forum which best suits the topic of your question. For example, questions about user interface issues would best be put in the [http://forums.lavag.org/User-Interface-f19.html user interface Forum], questions about hardware would go in the [http://forums.lavag.org/Hardware-f21.html hardware Forum]. Regardless of which Forum you post in, be detailed. Include as much pertinent information as possible in your question and also include all relevant system specs. Do not respond to a post located in the wrong forum to let the user know it's in the wrong forum. This is the job of the moderator since they have the power to move the post. Again, please use the report post to moderator button. Making comments of this fact is considered impersonating a moderator and is not acceptable.
*'''Update your personal profile''' information to include the current LV version you are using. This will help everyone answer your question properly and tailor it to the proper version you have. Unlike other forums, the number of posts you have does not reflect the experience you have using LV. Please be honest about your experience level. If you are a new user or an experienced professional, this should be reflected by specifying the year you started using LabVIEW in your profile.
*'''Don't cross-post'''. Cross-posting (asking the same question in more than one LAVA Forum) is pretty annoying, so people often ignore cross-posts. Even worse, your question may be deleted by a moderator (mod) or administator (admin). Don't worry, most users check most, if not all of the Forums, so your question will be answered. The reason for this policy is that cross-posts put irrelevant information which takes time to comb through. By avoiding redundant posts, the Forums are kept 'cleaner', thus, it makes it easier to find, and answer questions.
*'''Ask Questions the right way'''. Please help others trying to hep you by providing as much information as possible. Explain what the problem is, what you have done so far, what works, what does not work, etc. Here is an excellent link with more suggestions on [http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]
*'''Be nice to new LabVIEW Users'''. All of us were [http://en.wikipedia.org/wiki/Newbie new] once and many of us still consider ourselves new to LabVIEW even after months (or years) of programming. New LabVIEW users are prospective "Architects" and are therefore our most valuable resource. We must treat new users with kindness and patience — nothing scares potentially valuable contributors away faster than hostility or elitism. please follow the [[#The Golden Forum Rules|Golden Rules]] below for proper conduct. In general, do not post comments to any discussion about how the user will be better off on another website or forum.
*'''Don't abuse the PM''' (Personal Message System) Please don't PM people on these forums for LabVIEW technical support. Especially after you've already posted your question on the Forums. It is a personal choice for someone to respond to a question on the Forums. A PM is Personal (hence the name). Would you go around town knocking on the doors of people you don't know asking for LV help? No, so why would you do the same on the internet? Most of the time, a PM triggers an email notification to the recipient which can be even more annoying. Please think twice before sending a PM. If the person has not responded to your question on the Forums then what makes you think they will respond in person? I think your chances of getting a response from thousands of readers is better than just a response from one.... 'nuf said.
*'''Signature Size'''. Signatures may contain images, however to keep the page loading time and visual annoyance factor down to a minimum, ensure your graphical signatures do not exceed a maximum of 12,500 pixels or 15 kilobytes file size, whichever is reached first. Alternatively, three lines of text can be used as a signature. Do not pad out your text lines with blanks lines. A line of text is defined such that it does not wrap when viewed at a resolution of 640x480. If these limits are exceeded then you may be contacted by a moderator requesting an amendment to your signature. If none is made within a reasonable period of time, then a moderator may remove your signature from your profile.
*'''DON'T WRITE ALL IN CAPS'''. IT CAN BECOME VERY ANNOYING. CAPS ARE GENERALLY REGARDED AS YELLING, SO IF YOU WRITE ALL IN CAPS, FOLKS WILL THINK YOU ARE YELLING AT THEM, SO THEY WILL AVOID YOU. ALSO, CAPS LOOK ugly, so avoid writing all in caps.
*'''No flame wars''' (see glossary below). People obviously don't like to be insulted, so they will avoid flame wars. Flamers get a bad reputation, so their questions are more likely to be ignored.
*'''Spread the Love'''. The regulars would really appreciate it if you would acknowledge the helpfulness of their aid. Not only does praise make them love you, it helps them to understand if their help really was helpful. This way, they will know how to respond if they get a similar question again. This way, they can tailor their responses to better suit your needs.
*'''You may not use profanity'''. It is unprofessional and offensive and will not be tolerated. We have word filters in place for the most vulgar terms. Circumventing those word filters will result in punitive action.
*'''Editing previous posts'''. It is often better to edit than make a new post. Use your better judgment. At the bottom of each of your posts, you will find several icons. Click on the one that says 'Edit' in order to edit a post. You may only edit a post you have written, and there is a 24hr time limit on editions. Here are some general guidelines to follow when editing posts:
**Don't take out anything that may be required to understand the context of later posts
**Edit a previous post rather than make a new one. Use your judgment; sometimes it's necessary to make a new post.
**It's polite to sometimes list what was edited at the bottom of the post. If this ends up being longer than 2 lines, don't bother.
*'''We require all posts to be positive, constructive, and on topic'''. We reserve the right to remove any topics we deem inappropriate or disruptive to the LabVIEW community. Please note that, from time to time, topics may be removed for being inappropriate even though your individual post in that topic may have been perfectly fine. Please do not feel this reflects badly on you.
*'''No Spam'''. Spamming is not permitted; please keep all your posts as constructive and on-topic as possible. If you think a specific post is clearly spam use the report post to moderator button. Replying to such posts only adds visibility to them and makes the problem worse.

== Homework hustlers ==

Homework hustlers are those forum visitors that ask questions on the forums trying to get an easy solution to a school assignment. They do not try to put any effort on their own to solve the school assignment and want other forum members to give them the answer or solution to their problem. Homework Hustlers are not allowed on the Forums. No exceptions.

If you think a certain post is a homework hustling type question. Click on the report post to moderator button. This is the only recourse available to you. DO NOT respond to the post. You are not a moderator and posting negative or disrespectful comments will be considered abuse and results in a penalty by suspension of your account for a period of 2 days (see [[#Penalties for guideline and golden rule violations]]). If a post has been determined to be a Homework question, the guilty party will be contacted via PM and a clarification will be requested. If the issue is still not resolved to the satisfaction of a moderator, then the users' account will be deleted and all their posts removed.

== Glossary of useful forum terms ==

#Admin - (shortened form of Administrator); The ultimate gods of the Forums. They make the final decision on who can be banned, and other life-threatening questions.
#Banned - This is when you are not allowed to make anymore posts. Your IP address, E-mail address, and user name will prevent you to make anymore posts. This is extreeeeemly rare, and is preceded by a warning.
#LabVIEW FAQ - Frequently asked questions. The best resource for common questions.
#Flame war - a deliberate exchange of insults between two parties. This usually involves a series of insulting, irrelevant posts in the same thread.
#Kill - To delete a post.
#LQTM - Laughs Quietly To Myself - similar to, but usually more honest than, LOL (see below).
#LOL - Laughs Out loud.
#RMB - Right menu Button (used in LabVIEW)
#AFAIK - As far as I know
#Nuke - To maliciously destroy a thread.
#Mod - shortened form of Moderator); A moderator who has been given the power to delete/edit other people's posts. They are there to ensure that discussions are relevant and interesting. Don't worry, they only use their powers very sparingly. The moderators were chosen by God himself. God, what with being all-knowing and stuff, chose enough moderators to handle the load. Please don't ask to be made a moderator. We have enough, and you will only be disappointed.
#OCG - Modern, and [http://www.qwantz.com/archive/001057.html slightly crude], interpretation to OMG (see below).
#OMG - Oh My God or Oh My Gosh - an expression of exclaimation.
#Regular - Someone who lives on the Forums. Their diet usually consists of waffles, syrup and Mountain Dew. Renowned for their general friendliness, regulars are far from being extinct. But please, support their cause by donating generously to the Poor Boy Foundation
#Thread - A topic started by one member to which anyone can reply. Discussions should be about the original topic.
#PM - Private Message
#IMHO - In my humble opinion, used to express one's meaning

== File downloads in the forums==

An important thing to keep in mind. This is of course, a public space and it behooves you and the health of your computer to take care in clicking on any links/files of unknown origin that someone may post in a thread. Sad as it may seem, there are unsocialized bone nuts out there that get their jollies by causing mayhem. Due to the immediate nature of the forums, we can't insure that a damaging file won't find its way onto the site, though we'll make every effort to keep things safe by removing them ASAP. Please inform the Forum admin or any moderators you see wandering around if you spy something suspicious. Exercise caution and keep your common sense meter turned on and properly calibrated. We cannot be held responsible for the content posted by other Forum users. It may very well happen that something posted, be it text, images, files, or links to any of these thing may be offensive to you. The LAVA moderators will do the best they can to keep the Forums clean of offensive posts, but with such a large community, it is impossible to screen every post quickly and efficiently. Also keep in mind that we highly regard free speech, so the protection of that right will be utmost in deeming what is appropriate. If you have any specific complaint about something offensive you have seen, please feel free to contact a moderator or administrator. The best prevention is sound judgment.

Information about file downloads in the [http://forums.lavag.org/downloads.html Code Repository] can be found [http://forums.lavag.org/Code-Repository-Discussions-f62.html here]:

== The golden forum rules ==

#There will be no excessive use of profanity.
#Do not abuse the PM system
#There will be no racial, ethnic, gender based insults or any other personal discriminations.
#There will be no posts meant to offend or hurt any other member, in a manner which is offensive or inflammatory. Respect new members trying to learn LabVIEW.
#Spamming is not permitted; please keep all your posts as constructive and on-topic as possible.
#Pornography, warez, or any other illegal transactions may NOT be linked in any shape or form.
#All posts are property of the poster. This forum and all web sites owned in conjunction with this forum have the right to request alteration or deletion of any offensive post. Posts may be deleted for any reasons the forum administrators or moderators deem reasonable.
#Users may not argue a moderators decision publicly. Any and all complaints directed at a moderator must first address the moderator in question via PM. If the problem can not be resolved, then the moderator and user must send their positions to the forum admin. The forum admin will make or change any and/or all final decisions.
#Pictures may be posted as long as they are not explicit or offensive.
#Please keep foul language to a minimum, any excessive un-called for language will be removed and you will receive a final warning.
#Remember to post in the correct forum. Take your time to look at other topics and see where your topic should go. If your topic is placed in the wrong forum, it will be moved by a moderator.
#If a topic is recognized as being posted in the wrong forum, or if the post is a violation of our guidelines then please contact a moderator via the "! REPORT" post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a appropriateness of a member's topic will be sent a PM warning and placed into moderation queue upon further actions.
#Having fun is good, we like fun. There are general forums for non-programming related topics. Please keep it positive and polite. We do not censor opinions or ideas on our forums but we do take action against posts and/or topics that could cause unrest in the community beyond a civil and polite disagreement. If you beleive that a post and/or thread fits this critereon then please contact a moderator via the "! REPORT" post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a appropriateness of a member's will be sent a PM warning and placed into moderation queue upon further actions.
#Any impersonation of a user, Admin or moderator, in any mode of communication, is strictly prohibited and will result in a banning.
#Linked and locked topics are pruned regularly to reduce page clutter. If you have a question about where your topic went, please PM (personal message) a Moderator or Administrator before starting a new topic asking where it went, or posting a duplicate of the original topic. We will be happy to provide you with a link to the new location, or a reason why it was locked and/or removed.
#Homework Hustlers are not allowed on the Forums. No exceptions.
#LabVIEW serial number or registration key requests are NOT allowed. No exceptions.

== Penalties for guideline and golden rule violations ==

*Anyone found breaking the above rules and guidelines will have their account suspended for two (2) days.
*Anyone abusing the PM system will have their account suspended for four (4) days.
*If you repeatedly break the rules, your account will be permanently deleted and a ban placed on your registration info to prevent the account from being reused in the future.

All moderator decisions and outcomes (suspensions, deletions etc) will be kept private and confidential. This will allow offenders to recover from what may possibly be a mistake or error on their part or on the part of the moderators.

== Note ==
Only the moderators are authorized by the LAVA Forums to perform any user account suspension/deletion, post editing, post deletion and post moving. In addition, only moderators can decide if a post is a Homework question. Moderators do not read every post. This is impossible. Please use the '''report post to moderator''' button to bring anything to the attention of a moderator.
----

Remember, being a nice netizen will lead to respect, which leads to prompt answers and much fun. Do your best to be cordial, and you will see what a great thing the LabVIEW community is. If you have any questions about any issue brought up by this thread, feel free to ask the moderators, or your fellow Forumites.
Above all, have a nice day

== See also ==
*[http://forums.lavag.org/Tutorials-f72.html Tutorials on Using the Forums]
*[http://forums.lavag.org/Site-Feedback-and-Support-f27.html General Forums Feedback & Support]
*[http://forums.lavag.org/Suggestions-and-Ideas-f67.html Post Suggestions and Ideas for the Forums]
*[http://forums.lavag.org/Bug-Reports-f66.html Report a Forum Bug]

== External links ==
*[http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]

[[category:LAVA]]

List of LabVIEW Champions

2012-08-16T18:27:50Z

Crelf:

{{see also|LabVIEW Champion|LabVIEW Champions program FAQ}}
{| class="wikitable sortable"
|-
! Name
! Champion Since
! Expertise
! NI Certification
! Home
|-
| [[Albert Geven (LabVIEW Champion)|Albert Geven]]
| 2005
| LabVIEW, Algol-60, Applesoft, Pascal, Modula 2, C/C++
| CLA
| Netherlands
|-
| [[Alessandro Ricco (LabVIEW Champion)|Alessandro Ricco]]
| 2006
| LabVIEW, Java
|
| Italy
|-
| [[André Manzolli (LabVIEW Champion)|André Manzolli]]
| 2006
| LabVIEW, Visual Basic, C
| CLD
| Brazil
|-
| [[Ben Rayner (LabVIEW Champion)|Ben Rayner]]
| 2005
| LabVIEW, DSC, LV RT
| CLA
| United States
|-
| [[Bill Meier (LabVIEW Champion)|Bill Meier]]
| 2010
| LabVIEW, Visual Basic, Basic, Java, Fortran, Pascal, Cobol
| CLAD
| United States
|-
| [[Bogdan Iwinski (LabVIEW Champion)|Bogdan Iwinski]]
| 2010
| LabVIEW
| CLD, CPI
| Poland
|-
| [[Brett Percy (LabVIEW Champion)|Brett Percy]]
| 2006
| LabVIEW, TestStand, C/C++, Objective C, Assembler
| CLD
| Australia
|-
| [[Bruce Ammons (LabVIEW Champion)|Bruce Ammons]]
| 2005
| LabVIEW, C, Fortran, Basic
| CLD
| United States
|-
| [[Buddy Haun (LabVIEW Champion)|Buddy Haun]]
| 2006
| LabVIEW
| CLA, CPI
| United States
|-
| [[Charles Ghommidh (LabVIEW Champion)|Charles Ghommidh]]
| 2005
| LabVIEW
|
| France
|-
| [[Christian Altenbach (LabVIEW Champion)|Christian Altenbach]]
| 2005
| LabVIEW, Fortran
| CLAD
| United States
|-
| [[Christophe Salzmann (LabVIEW Champion)|Christophe Salzmann]]
| 2010
| LabVIEW, C, Matlab, Javascript
| NICI
| United States
|-
| [[Christopher G. Relf (LabVIEW Champion)|Christopher G. Relf]]
| 2005
| LabVIEW, TestStand, SignalExpress, NI-Vision, Vision Builder, LV RT, LV FPGA, Synchronized DAQ, LV PDA, GOOP
| CLA, CTD, CPI
| United States
|-
| [[Darin Kinion (LabVIEW Champion)|Darin Kinion]]
| 2012
| LabVIEW, C++, Fortran, Python
|
| United States
|-
| [[David Thomson (LabVIEW Champion)|David Thomson]]
| 2005
| LabVIEW, LV RT, LV FPGA, LV PDA
| CLA
| United States
|-
| [[Dennis Knutson (LabVIEW Champion)|Dennis Knutson]]
| 2005
| LabVIEW
|
| United States
|-
| [[Ed Dickens (LabVIEW Champion)|Ed Dickens]]
| 2005
| LabVIEW, LV RT, LV FPGA
| CLA, CPI
| United States
|-
| [[Fabiola De la Cueva (LabVIEW Champion)|Fabiola De la Cueva]]
| 2012
| LabVIEW, C/C++ and Java
| CLA, CPI
| United States
|-
| [[Jack Dunaway (LabVIEW Champion)|Jack Dunaway]]
| 2010
| LabVIEW, LVOOP, UX
| CLA
| United States
|-
| [[Jeff Bohrer (LabVIEW Champion)|Jeff Bohrer]]
| 2012
| LabVIEW, TestStand
| CLD
| United States
|-
| [[Jim Kring (LabVIEW Champion)|Jim Kring]]
| 2005
| LabVIEW, Python, PHP
| CLA
| United States
|-
| [[Joe Hoskins (LabVIEW Champion)|Joe Hoskins]]
| 2010
| LabVIEW
|
| United States
|-
| [[Jonathon Green (LabVIEW Champion)|Jonathon Green]]
| 2012
| LabVIEW
| CLA
| Australia
|-
| [[Justin Goeres (LabVIEW Champion)|Justin Goeres]]
| 2012
| LabVIEW, PHP
| CLA
| United States
|-
| [[Leigh Christian (LabVIEW Champion)|Leigh Christian]]
| 2010
| LabVIEW
|
| United States
|-
| [[Mark Balla (LabVIEW Champion)|Mark Balla]]
| 2010
| LabVIEW
| CLA
| United States
|-
| [[Mark Yedinak (LabVIEW Champion)|Mark Yedinak]]
| 2010
| LabVIEW, C/C++
| CLA
| United States
|-
| [[Michael Aivaliotis (LabVIEW Champion)|Michael Aivaliotis]]
| 2005
| LabVIEW, LV RT, TestStand
| CLA
| Canada
|-
| [[Mike Porter (LabVIEW Champion)|Mike Porter]]
| 2005
| LabVIEW
|
| United States
|-
| [[Nancy Hollenback (LabVIEW Champion)|Nancy Hollenback]]
| Champion Emeritus
| LabVIEW
|

| United States
|-
| [[Norm Kirchner (LabVIEW Champion)|Norm Kirchner]]
| Champion Emeritus
| LabVIEW
|
| United States
|-
| [[Parag Deshpande (LabVIEW Champion)|Parag Deshpande]]
| 2012
| LabVIEW, TestStand, MATLAB, Simulink, C#, SQL
| CLA
| India
|-
| [[Pavan Bathla (LabVIEW Champion)|Pavan Bathla]]
| 2007
| LabVIEW, C/C++, CVI, VB, TestStand, LV RT, LV FPGA, Matlab, UML, GOOP
|
| United States
|-
| [[Piotr Maj (LabVIEW Champion)|Piotr Maj]]
| 2012
| LabVIEW
| CLD, CPI
| Poland
|-
| [[Putnam W. Monroe Jr. (LabVIEW Champion)|Putnam W. Monroe Jr.]]
| 2005
| LabVIEW
| CLD
| United States
|-
| [[Ray Robichaud (LabVIEW Champion)|Ray Robichaud]]
| 2005
| LabVIEW, LabWindows-CVI, C/C++
|
| Canada
|-
| [[Rick Beauchaine (LabVIEW Champion)|Rick Beauchaine]]
| 2005
| LabVIEW
| CLA
| United States
|-
| [[Richard Thomas (LabVIEW Champion)|Richard Thomas]]
| 2012
| LabVIEW, LV RT, LV FPGA
| CLA
| England
|-
| [[Rolf Kalbermatter (LabVIEW Champion)|Rolf Kalbermatter]]
| 2010
| LabVIEW, Pascal, C/C++, Java, Lua, Python
| CLD
| Netherlands
|-
| [[Samuel James (LabVIEW Champion)|Samuel James]]
| 2012
| LabVIEW
| CLA
| India
|-
| [[Saverio Mercurio (LabVIEW Champion)|Saverio Mercurio]]
| 2010
| LabVIEW
|
| United States
|-
| [[Scott Hannahs (LabVIEW Champion)|Scott Hannahs]]
| 2005
| LabVIEW, C
|
| United States
|-
| [[Shane O'Neill (LabVIEW Champion)|Shane O'Neill]]
| 2010
| LabVIEW
|
| United States
|-
| [[Tomi Maila (LabVIEW Champion)|Tomi Maila]]
| 2007
| LabVIEW, C/C++, MATLAB, Perl, PHP, Java, Scala, Haskell
| CLAD
| Finland
|-
| [[Urs Lauterburg (LabVIEW Champion)|Urs Lauterburg]]
| 2005
| LabVIEW
|
| Switzerland
|-
| [[Yair Neeman (LabVIEW Champion)|Yair Neeman]]
| 2007
| LabVIEW
|
| Israel
|-
| [[Zbigniew Sobków (LabVIEW Champion)|Zbigniew Sobków]]
| 2005
| LabVIEW
| CLD, CPI
| Poland
|}

[[Category:LabVIEW Champions]]
[[Category:Lists]]

OpenG Submission Process

2011-11-01T14:41:10Z

Crelf: Blanked the page

OpenG Release Process

2011-11-01T14:40:45Z

Crelf: Blanked the page

OpenG Release Process

2011-11-01T14:30:38Z

Crelf: Created page with " Placeholder"

Placeholder

OpenG Submission Process

2011-11-01T14:30:05Z

Crelf: Created page with " Placeholder"

Placeholder

LabVIEW configuration file

2011-02-10T16:35:06Z

Crelf:

This article contains information related to the LabVIEW configuration file. This file is used by LabVIEW to store configuration information related to the LabVIEW development environment. If you are interested in finding out how to read and write your own [[Configuration file]] then see the article on the [[Configuration file|configuration file VIs]].

== Editing the LabVIEW configuration file - A disclaimer ==

The options that aren't in the preferences dialog are generally considered to be not useful or even harmful. They are sometimes there to allow National Instruments a backdoor or a workaround for when the LabVIEW development team changes a behavior. They are also used to turn on obscure development features that the developers use to make or debug LabVIEW. These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful.

The LabVIEW developers have never tried to hide any of these strings, but it is unlikely that you will gain any benefit from trying out various combinations of the settings. If you ask technical support what a setting is, they will likely tell you that they have no idea. They are telling you the truth.

Even some of the folks in NI R&D may not know what some of the settings do without checking the code. Others, such as exoticcontrols, no longer do anything. It was once used to show a control palette submenu that contained controls that were still in work and not ready for prime-time. They were experiments, unsupported features, and guaranteed to crash if you did much with them. Just the sort of thing that is needed for development, but not useful to even advanced LabVIEW users unless they have a death-wish.

If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LabVIEW left it. Don't ask tech support to fix it or complain that the LabVIEW attic has rusty nails and splinters. Resedit is a low level tool that in the right hands is useful, in the wrong hands, well, its in the wrong hands. For the person that likes taking a multimeter and a soldering iron to computers and household appliances, its exactly what you always wanted. If you start monkeying with things in the resources or the .ini file, use common sense and do it on a copy or you will just end up reinstalling LabVIEW.

Once the fun and experimentation is over with, I think you will agree that the useful options, with very few exceptions are in the Preferences dialog.

== Settings Descriptions ==

This is a relatively comprehensive list of the settings that can be included in a labview.ini file (or a compiled executable's ini file). While some of these settings appear in the files by default, others may only appear when the features used require them to be there. Some settings can only be added manually to provide access to back door features and operations.

LabVIEW configuration keys are organized into the following categories (in alphabetical order):

*[[LabVIEW configuration file/Block Diagram|Block Diagram]]
*[[LabVIEW configuration file/Colors|Colors]]
*[[LabVIEW configuration file/Debugging|Debugging]]
*[[LabVIEW configuration file/Execution System|Execution System]]
*[[LabVIEW configuration file/Fonts|Fonts]]
*[[LabVIEW configuration file/Front Panel|Front Panel]]
*[[LabVIEW configuration file/Getting Started Window|Getting Started Window]]
*[[LabVIEW configuration file/History|History]]
*[[LabVIEW configuration file/Miscellaneous|Miscellaneous]]
*[[LabVIEW configuration file/Paths|Paths]]
*[[LabVIEW configuration file/Performance|Performance]]
*[[LabVIEW configuration file/Printing|Printing]]
*[[LabVIEW configuration file/Time and Date|Time and Date]]
*[[LabVIEW configuration file/VI Server|VI Server]]
*[[LabVIEW configuration file/Web Server|Web Server]]
*[[LabVIEW configuration file/Unknown|Uncategorized]] - Do you recognize any of these? Move them to the right place!
*[[LabVIEW configuration file/Easter Eggs|Easter Eggs]] - Reveal hidden messages and features (no functional advantage. Just for fun)

 '''Editor's Note:''' To add new configuration keys to any of the above pages, please use the [[Template:Labviewconfigurationkey|LabVIEW Configuration Key Template]]

----

== See Also ==

*[[Custom LabVIEW configuration file]]

== External Links ==

*[http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/customizing_your_work_environment/#How_LabVIEW_Stores_Options NI.com online help for LV configuration files]
*[http://sthmac.magnet.fsu.edu/labview/LVOptionsList.html Scott Hannahs's LabVIEW Info Page]

[[Category:Configuration File]]
[[Category:Development environment]]

LabVIEW configuration file

2011-02-10T16:34:38Z

Crelf: Changed "Unknown" group name to "Uncategorized"

This article contains information related to the LabVIEW configuration file. This file is used by LabVIEW to store configuration information related to the LabVIEW development environment. If you are interested in finding out how to read and write your own [[Configuration file]] then see the article on the [[Configuration file|configuration file VIs]].

== Editing the LabVIEW configuration file - A disclaimer ==

The options that aren't in the preferences dialog are generally considered to be not useful or even harmful. They are sometimes there to allow National Instruments a backdoor or a workaround for when the LabVIEW development team changes a behavior. They are also used to turn on obscure development features that the developers use to make or debug LabVIEW. These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful.

The LabVIEW developers have never tried to hide any of these strings, but it is unlikely that you will gain any benefit from trying out various combinations of the settings. If you ask technical support what a setting is, they will likely tell you that they have no idea. They are telling you the truth.

Even some of the folks in NI R&D may not know what some of the settings do without checking the code. Others, such as exoticcontrols, no longer do anything. It was once used to show a control palette submenu that contained controls that were still in work and not ready for prime-time. They were experiments, unsupported features, and guaranteed to crash if you did much with them. Just the sort of thing that is needed for development, but not useful to even advanced LabVIEW users unless they have a death-wish.

If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LabVIEW left it. Don't ask tech support to fix it or complain that the LabVIEW attic has rusty nails and splinters. Resedit is a low level tool that in the right hands is useful, in the wrong hands, well, its in the wrong hands. For the person that likes taking a multimeter and a soldering iron to computers and household appliances, its exactly what you always wanted. If you start monkeying with things in the resources or the .ini file, use common sense and do it on a copy or you will just end up reinstalling LabVIEW.

Once the fun and experimentation is over with, I think you will agree that the useful options, with very few exceptions are in the Preferences dialog.

== Settings Descriptions ==

This is a relatively comprehensive list of the settings that can be included in a labview.ini file (or a compiled executable's ini file). While some of these settings appear in the files by default, others may only appear when the features used require them to be there. Some settings can only be added manually to provide access to back door features and operations.

LabVIEW configuration keys are organized into the following categories (in alphabetical order):

*[[LabVIEW configuration file/Block Diagram|Block Diagram]]
*[[LabVIEW configuration file/Colors|Colors]]
*[[LabVIEW configuration file/Debugging|Debugging]]
*[[LabVIEW configuration file/Execution System|Execution System]]
*[[LabVIEW configuration file/Fonts|Fonts]]
*[[LabVIEW configuration file/Front Panel|Front Panel]]
*[[LabVIEW configuration file/Getting Started Window|Getting Started Window]]
*[[LabVIEW configuration file/History|History]]
*[[LabVIEW configuration file/Miscellaneous|Miscellaneous]]
*[[LabVIEW configuration file/Paths|Paths]]
*[[LabVIEW configuration file/Performance|Performance]]
*[[LabVIEW configuration file/Printing|Printing]]
*[[LabVIEW configuration file/Time and Date|Time and Date]]
*[[LabVIEW configuration file/VI Server|VI Server]]
*[[LabVIEW configuration file/Web Server|Web Server]]
*[[LabVIEW configuration file/Unknown|Uncategorized]] Do you recognize any of these? Move them to the right place!
*[[LabVIEW configuration file/Easter Eggs|Easter Eggs]] Reveal hidden messages and features (no functional advantage. Just for fun)

 '''Editor's Note:''' To add new configuration keys to any of the above pages, please use the [[Template:Labviewconfigurationkey|LabVIEW Configuration Key Template]]

----

== See Also ==

*[[Custom LabVIEW configuration file]]

== External Links ==

*[http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/customizing_your_work_environment/#How_LabVIEW_Stores_Options NI.com online help for LV configuration files]
*[http://sthmac.magnet.fsu.edu/labview/LVOptionsList.html Scott Hannahs's LabVIEW Info Page]

[[Category:Configuration File]]
[[Category:Development environment]]

LabVIEW configuration file/Getting Started Window

2011-02-10T16:25:00Z

Crelf: Added GSW_RSSCheckEnabled

This is a list of LabVIEW ini File settings relating to the Getting Started Window.

{{TOCright}}

{{ labviewconfigurationkey
| keyname =GSW_RSSCheckEnabled
| example =GSW_RSSCheckEnabled=FALSE
| datatype =b
| description =Stop LabVIEW from checking ni.com for updates to the "Latest from ni.com", "Online Support" and "Help" lists.
| permitted_values =TRUE or FALS
| default =TRUE
| LV1 = 2009
| LV2 = 2010
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}

{{ labviewconfigurationkey
| keyname =MaxGSWRecentProjects
| example =MaxGSWRecentProjects=5
| datatype =i
| description =Set the number of recently opened projects in the "Open" list of the Getting Started Window
| permitted_values =0...
| default =2
| LV1 = 2009
| LV2 = 2010
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}

LabVIEW configuration file/Getting Started Window

2011-02-10T16:21:28Z

Crelf: Spelling correction

This is a list of LabVIEW ini File settings relating to the Getting Started Window.

{{TOCright}}

{{ labviewconfigurationkey
| keyname =MaxGSWRecentProjects
| example =MaxGSWRecentProjects=5
| datatype =i
| description =Set the number of recently opened projects in the "Open" list of the Getting Started Window
| permitted_values =0...
| default =2
| LV1 = 2009
| LV2 = 2010
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}

LabVIEW configuration file/Getting Started Window

2011-02-10T16:20:27Z

Crelf: Initial page creation, added MaxGSWRecentProjects

This is a list of LabVIEW ini File settings relating to teh Getting Started Window.

{{TOCright}}

{{ labviewconfigurationkey
| keyname =MaxGSWRecentProjects
| example =MaxGSWRecentProjects=5
| datatype =i
| description =Set the number of recently opened projects in the "Open" list of the Getting Started Window
| permitted_values =0...
| default =2
| LV1 = 2009
| LV2 = 2010
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}

LabVIEW configuration file

2011-02-10T16:16:57Z

Crelf: Added Getting Started Window

This article contains information related to the LabVIEW configuration file. This file is used by LabVIEW to store configuration information related to the LabVIEW development environment. If you are interested in finding out how to read and write your own [[Configuration file]] then see the article on the [[Configuration file|configuration file VIs]].

== Editing the LabVIEW configuration file - A disclaimer ==

The options that aren't in the preferences dialog are generally considered to be not useful or even harmful. They are sometimes there to allow National Instruments a backdoor or a workaround for when the LabVIEW development team changes a behavior. They are also used to turn on obscure development features that the developers use to make or debug LabVIEW. These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful.

The LabVIEW developers have never tried to hide any of these strings, but it is unlikely that you will gain any benefit from trying out various combinations of the settings. If you ask technical support what a setting is, they will likely tell you that they have no idea. They are telling you the truth.

Even some of the folks in NI R&D may not know what some of the settings do without checking the code. Others, such as exoticcontrols, no longer do anything. It was once used to show a control palette submenu that contained controls that were still in work and not ready for prime-time. They were experiments, unsupported features, and guaranteed to crash if you did much with them. Just the sort of thing that is needed for development, but not useful to even advanced LabVIEW users unless they have a death-wish.

If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LabVIEW left it. Don't ask tech support to fix it or complain that the LabVIEW attic has rusty nails and splinters. Resedit is a low level tool that in the right hands is useful, in the wrong hands, well, its in the wrong hands. For the person that likes taking a multimeter and a soldering iron to computers and household appliances, its exactly what you always wanted. If you start monkeying with things in the resources or the .ini file, use common sense and do it on a copy or you will just end up reinstalling LabVIEW.

Once the fun and experimentation is over with, I think you will agree that the useful options, with very few exceptions are in the Preferences dialog.

== Settings Descriptions ==

This is a relatively comprehensive list of the settings that can be included in a labview.ini file (or a compiled executable's ini file). While some of these settings appear in the files by default, others may only appear when the features used require them to be there. Some settings can only be added manually to provide access to back door features and operations.

LabVIEW configuration keys are organized into the following categories (in alphabetical order):

*[[LabVIEW configuration file/Block Diagram|Block Diagram]]
*[[LabVIEW configuration file/Colors|Colors]]
*[[LabVIEW configuration file/Debugging|Debugging]]
*[[LabVIEW configuration file/Execution System|Execution System]]
*[[LabVIEW configuration file/Fonts|Fonts]]
*[[LabVIEW configuration file/Front Panel|Front Panel]]
*[[LabVIEW configuration file/Getting Started Window|Getting Started Window]]
*[[LabVIEW configuration file/History|History]]
*[[LabVIEW configuration file/Miscellaneous|Miscellaneous]]
*[[LabVIEW configuration file/Paths|Paths]]
*[[LabVIEW configuration file/Performance|Performance]]
*[[LabVIEW configuration file/Printing|Printing]]
*[[LabVIEW configuration file/Time and Date|Time and Date]]
*[[LabVIEW configuration file/VI Server|VI Server]]
*[[LabVIEW configuration file/Web Server|Web Server]]
*[[LabVIEW configuration file/Unknown|Unknown]] Do you recognize any of these?
*[[LabVIEW configuration file/Easter Eggs|Easter Eggs]] Reveal hidden messages and features (no functional advantage. Just for fun)

 '''Editor's Note:''' To add new configuration keys to any of the above pages, please use the [[Template:Labviewconfigurationkey|LabVIEW Configuration Key Template]]

----

== See Also ==

*[[Custom LabVIEW configuration file]]

== External Links ==

*[http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/customizing_your_work_environment/#How_LabVIEW_Stores_Options NI.com online help for LV configuration files]
*[http://sthmac.magnet.fsu.edu/labview/LVOptionsList.html Scott Hannahs's LabVIEW Info Page]

[[Category:Configuration File]]
[[Category:Development environment]]

Christopher G. Relf (LabVIEW Champion)

2009-04-25T19:24:35Z

Crelf:

{| class="wikitable"
|-
| '''Name'''
| Christopher G. Relf
|-
| '''Home'''
| Farmington Hills, MI
|-
| '''Certification'''
| Certified LabVIEW Architect, Certified Professional Instructor
|-
| '''Used LabVIEW Since:'''
| LabVIEW 3.0
|-
| '''Applications Areas'''
| System Integrator - Medical, Aerospace, Defense, Mining, Research and Development, Psychometric, Vision Systems
|}
== Biography: ==

Christopher G. Relf is the Chief Architect at [http://www.viengineering.com VI Engineering Inc] (a [http://www.ni.com National Instruments] [http://www.ni.com/alliance/member_levels.htm Select Alliance Partner]), and a freelance technical journalist currently contributing a monthly column in "[http://www.westwick-farrow.com.au/mags/default.asp?origin=process What's New in Process Technology]", published by [http://www.westwick-farrow.com.au Westwick-Farrow]. A keen software and hardware automation engineer, Christopher is a National Instruments [http://sine.ni.com/nips/cds/view/p/lang/en/nid/13477 Certified LabVIEW Architect] and the author of "[http://www.amazon.com/Image-Acquisition-Processing-LabVIEW/dp/0849314801/ref=sr_1_1?ie=UTF8&s=books&qid=1240687027&sr=8-1 Image Acquisition and Processing with LabVIEW]" ([http://crcpress.com/ CRC Press]). Christopher's industrial experience includes roles as the Development Manager / Senior Technical Specialist for [http://www.nvsi.com.au Neo Vista System Integrators Pty Ltd], an Automation Scientist at the Division of Telecommunications and Industrial Physics of the Australian [http://www.csiro.au/ Commonweath Scientific and Industrial Research Organisation] (CSIRO), a Process Software Engineer [http://www.jdsu.com JDS Uniphase] and as a freelance technical journalist for [http://www.acp.com.au/ Australian Consolidated Press].

=== Books: ===

*[http://www.amazon.com/exec/obidos/ASIN/0849314801/nationalinstrume Image Acquisition and Processing with LabVIEW (CRC Press)]
*[http://www.amazon.com/exec/obidos/ASIN/0849315867/nationalinstrume The Engineering Handbook 2nd &3rd Editions (CRC Press)]

=== Discussion Groups: ===

LAVA, Open-G, NI Discussion Forums

=== Websites: ===

*[http://forums.lavag.org/blog/crelfs_technology_articles/index.php? Crelf's Technology Article]

=== Articles ===

#"NeoLOG - Datalogging with LabVIEW Plug-ins" - 2005 NI-Week Case Study - Relf C. G.
#"Australian Square Kilometer Array Site Testing" - 2005 NI-Week Case Study - Relf C. G., Raynal L.
#"Athlete Psychology Testing System" - 2005 NI-Week Case Study - Relf C. G.
#"RF Compliance Test System" - 2005 NI-Week Case Study - Relf C. G., Bowyer G. K.
#"Wheat Grain Crush Curve Analysis System" - 2003 NI-Week Case Study - Bowyer G. K., Relf C. G.
#"Custom System Integration and Commercial Off-The-Shelf Products" - 2005 Information Circular
#"TEDS - Are You Ready?" - What's New in Process Technology
#"PACs versus PLCs - What are the Real Differences?" - What's New in Process Technology
#"Data Validity - Are Your Numbers Legit?" - What's New in Process Technology
#"Automated Object Inspection - Finally a Mature Technology" - What's New in Process Technology
#"50 Ton Load Cell Testing System" - 2004 NI-Week Case Study - Raynal L., Granger W., Relf C. G.
#"Printed Circuit Board (PCB) Automated Inspection System" - 2004 NI-Week Case Study - Relf C. G.
#"CAMS - Cable Analysis Measurement System" - 2004 NI-Week Case Study - Relf C. G.
#"Rail Line Scan - Overhead Line Alignment Measurement" - 2004 NI-Week Case Study - Relf C. G.
#"Laboratory Subject Monitoring and Stimuli Delivery System" - 2004 NI-Week Case Study - Bowyer G. K., Relf C. G.
#"Alphachron™ He Extraction/Measurement Instrument" - 2004 NI-Week Case Study - Raynal L., Relf C. G., McInnes B.
#"LabVIEW Software Engineering" - 2004 The Engineering Handbook (2nd Ed.)
#"Environmental Chamber Monitoring and Control" - 2003 NI-Week Case Study - Granger L., Dick R., Relf C. G.
#"LabVIEW Automates Eccentricity Measurement in an Industrial Production Line" - 2002 NI-Week Case Study - Relf C. G.
#“Automated Object Inspection – Finally a Mature Technology” - What's New in Process Technology
#“Automated Object Inspection – Front-End Components” - What's New in Process Technology
#“Automated Object Inspection – Shedding a Little Light on the Subject” - What's New in Process Technology
#“Feedback to Better Control your Processes” - What's New in Process Technology
#“Closed Loop Control – Common Models” - What's New in Process Technology
#“Industrial Automobile Networks – Driving the Data” - What's New in Process Technology
#“Deterministic Data Acquisition and Control with a Real-Time Operating System (Part 1)” - What's New in Process Technology
#“Deterministic Data Acquisition and Control with a Real-Time Operating System (Part 2)” - What's New in Process Technology

=== User Groups: ===

[[OpenG]] User Group, LabVIEW Advanced Virtual Architects ([[LAVA]]) User Group.

==See also==
*[[List of LabVIEW Champions]]
*[[LabVIEW Champions]]

[[category:LabVIEW Champions|Relf, Christopher G]]

Forum Guidelines

2008-12-07T23:35:33Z

Crelf: /* The golden forum rules */

__NOTOC__
{| align="right" border="0"
|__TOC__
|-
|}
== Introduction ==

'''These rules and guidelines apply to the LAVA [http://forums.lavag.org/forums.html Forums] and all the discussion threads associated with the Wiki articles.''' For Guidelines pertaining to other areas of the site see:

*[[LabVIEW Wiki:Policies and guidelines|LabVIEW Wiki Policies and Guidelines]]
*[[Help:Contents|Complete LabVIEW Wiki Help, FAQ and Guidelines]]
*[http://forums.lavag.org/Code-Repository-Discussions-f62.html Code Repository Information and Procedure]

The LAVA Forums are managed and maintained by dedicated LabVIEW enthusiasts like yourself. We are volunteers committed to the development of an open and unbiased exchange of ideas on intermediate to advanced topics in LabVIEW. The document that follows covers key areas of the Forums and should answer most of your questions regarding features, proper usage and etiquette.

== Finding information ==

'''Use Search.''' Your question has probably already been answered. Before posting a LabVIEW question we recommend that you try checking the [[Portal:LabVIEW FAQ|LabVIEW FAQ]] and if your question is still not answered, [http://forums.lavag.org/labviewsearch.html Search the Forums]. A link for searching the Forums can be found in the top header banner at the top right of all pages in the Forums.

== Contributing and posting in the forums ==

*'''Use images'''. Images are the best way to convey the problem you are having. In LabVIEW this is more important because of the graphical nature of the language. You cannot include text code like you would in C++ or other languages. Please check our [http://forums.lavag.org/How-to-Insert-Images-in-your-Posts-t771.html Guide] for how to post images.
*'''Upload example code'''. We love that here. Please upload your code that you are having problems with. You can include all your code into a single [[llb]] or just include all vi's into a *.zip file format. If certain files are missing then it will be more difficult for others to help you with your problem. You will be surprised how many people are willing to re-write your code and make suggestions for you. This can only happen with functional code. Are you uploading code in response to a question? If so then please respect the recipient's LabVIEW version. If you can, perform a save to previous version on your code so they can open it up in their LabVIEW development environment. If the code is very simple and is contained on one diagram then you might want to consider posting an image of the solution instead.
*'''Post in the right Forum'''. Choose a Forum which best suits the topic of your question. For example, questions about user interface issues would best be put in the [http://forums.lavag.org/User-Interface-f19.html user interface Forum], questions about hardware would go in the [http://forums.lavag.org/Hardware-f21.html hardware Forum]. Regardless of which Forum you post in, be detailed. Include as much pertinent information as possible in your question and also include all relevant system specs. Do not respond to a post located in the wrong forum to let the user know it's in the wrong forum. This is the job of the moderator since they have the power to move the post. Again, please use the report post to moderator button. Making comments of this fact is considered impersonating a moderator and is not acceptable.
*'''Update your personal profile''' information to include the current LV version you are using. This will help everyone answer your question properly and tailor it to the proper version you have. Unlike other forums, the number of posts you have does not reflect the experience you have using LV. Please be honest about your experience level. If you are a new user or an experienced professional, this should be reflected by specifying the year you started using LabVIEW in your profile.
*'''Don't cross-post'''. Cross-posting (asking the same question in more than one LAVA Forum) is pretty annoying, so people often ignore cross-posts. Even worse, your question may be deleted by a moderator (mod) or administator (admin). Don't worry, most users check most, if not all of the Forums, so your question will be answered. The reason for this policy is that cross-posts put irrelevant information which takes time to comb through. By avoiding redundant posts, the Forums are kept 'cleaner', thus, it makes it easier to find, and answer questions.
*'''Ask Questions the right way'''. Please help others trying to hep you by providing as much information as possible. Explain what the problem is, what you have done so far, what works, what does not work, etc. Here is an excellent link with more suggestions on [http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]
*'''Be nice to new LabVIEW Users'''. All of us were [http://en.wikipedia.org/wiki/Newbie new] once and many of us still consider ourselves new to LabVIEW even after months (or years) of programming. New LabVIEW users are prospective "Architects" and are therefore our most valuable resource. We must treat new users with kindness and patience — nothing scares potentially valuable contributors away faster than hostility or elitism. please follow the [[#The Golden Forum Rules|Golden Rules]] below for proper conduct. In general, do not post comments to any discussion about how the user will be better off on another website or forum.
*'''Don't abuse the PM''' (Personal Message System) Please don't PM people on these forums for LabVIEW technical support. Especially after you've already posted your question on the Forums. It is a personal choice for someone to respond to a question on the Forums. A PM is Personal (hence the name). Would you go around town knocking on the doors of people you don't know asking for LV help? No, so why would you do the same on the internet? Most of the time, a PM triggers an email notification to the recipient which can be even more annoying. Please think twice before sending a PM. If the person has not responded to your question on the Forums then what makes you think they will respond in person? I think your chances of getting a response from thousands of readers is better than just a response from one.... 'nuf said.
*'''Signature Size'''. Signatures may contain images, however to keep the page loading time and visual annoyance factor down to a minimum, ensure your graphical signatures do not exceed a maximum of 12,500 pixels or 15 kilobytes file size, whichever is reached first. Alternatively, three lines of text can be used as a signature. Do not pad out your text lines with blanks lines. A line of text is defined such that it does not wrap when viewed at a resolution of 640x480. If these limits are exceeded then you may be contacted by a moderator requesting an amendment to your signature. If none is made within a reasonable period of time, then a moderator may remove your signature from your profile.
*'''DON'T WRITE ALL IN CAPS'''. IT CAN BECOME VERY ANNOYING. CAPS ARE GENERALLY REGARDED AS YELLING, SO IF YOU WRITE ALL IN CAPS, FOLKS WILL THINK YOU ARE YELLING AT THEM, SO THEY WILL AVOID YOU. ALSO, CAPS LOOK ugly, so avoid writing all in caps.
*'''No flame wars''' (see glossary below). People obviously don't like to be insulted, so they will avoid flame wars. Flamers get a bad reputation, so their questions are more likely to be ignored.
*'''Spread the Love'''. The regulars would really appreciate it if you would acknowledge the helpfulness of their aid. Not only does praise make them love you, it helps them to understand if their help really was helpful. This way, they will know how to respond if they get a similar question again. This way, they can tailor their responses to better suit your needs.
*'''You may not use profanity'''. It is unprofessional and offensive and will not be tolerated. We have word filters in place for the most vulgar terms. Circumventing those word filters will result in punitive action.
*'''Editing previous posts'''. It is often better to edit than make a new post. Use your better judgment. At the bottom of each of your posts, you will find several icons. Click on the one that says 'Edit' in order to edit a post. You may only edit a post you have written, and there is a 24hr time limit on editions. Here are some general guidelines to follow when editing posts:
**Don't take out anything that may be required to understand the context of later posts
**Edit a previous post rather than make a new one. Use your judgment; sometimes it's necessary to make a new post.
**It's polite to sometimes list what was edited at the bottom of the post. If this ends up being longer than 2 lines, don't bother.
*'''We require all posts to be positive, constructive, and on topic'''. We reserve the right to remove any topics we deem inappropriate or disruptive to the LabVIEW community. Please note that, from time to time, topics may be removed for being inappropriate even though your individual post in that topic may have been perfectly fine. Please do not feel this reflects badly on you.
*'''No Spam'''. Spamming is not permitted; please keep all your posts as constructive and on-topic as possible. If you think a specific post is clearly spam use the report post to moderator button. Replying to such posts only adds visibility to them and makes the problem worse.

== Homework hustlers ==

Homework hustlers are those forum visitors that ask questions on the forums trying to get an easy solution to a school assignment. They do not try to put any effort on their own to solve the school assignment and want other forum members to give them the answer or solution to their problem. Homework Hustlers are not allowed on the Forums. No exceptions.

If you think a certain post is a homework hustling type question. Click on the report post to moderator button. This is the only recourse available to you. DO NOT respond to the post. You are not a moderator and posting negative or disrespectful comments will be considered abuse and results in a penalty by suspension of your account for a period of 2 days (see [[#Penalties for guideline and golden rule violations]]). If a post has been determined to be a Homework question, the guilty party will be contacted via PM and a clarification will be requested. If the issue is still not resolved to the satisfaction of a moderator, then the users' account will be deleted and all their posts removed.

== Glossary of useful forum terms ==

#Admin - (shortened form of Administrator); The ultimate gods of the Forums. They make the final decision on who can be banned, and other life-threatening questions.
#Banned - This is when you are not allowed to make anymore posts. Your IP address, E-mail address, and user name will prevent you to make anymore posts. This is extreeeeemly rare, and is preceded by a warning.
#LabVIEW FAQ - Frequently asked questions. The best resource for common questions.
#Flame war - a deliberate exchange of insults between two parties. This usually involves a series of insulting, irrelevant posts in the same thread.
#Kill - To delete a post.
#LQTM - Laughs Quietly To Myself - similar to, but usually more honest than, LOL (see below).
#LOL - Laughs Out loud.
#RMB - Right menu Button (used in LabVIEW)
#AFAIK - As far as I know
#Nuke - To maliciously destroy a thread.
#Mod - shortened form of Moderator); A moderator who has been given the power to delete/edit other people's posts. They are there to ensure that discussions are relevant and interesting. Don't worry, they only use their powers very sparingly. The moderators were chosen by God himself. God, what with being all-knowing and stuff, chose enough moderators to handle the load. Please don't ask to be made a moderator. We have enough, and you will only be disappointed.
#OCG - Modern, and [http://www.qwantz.com/archive/001057.html slightly crude], interpretation to OMG (see below).
#OMG - Oh My God or Oh My Gosh - an expression of exclaimation.
#Regular - Someone who lives on the Forums. Their diet usually consists of waffles, syrup and Mountain Dew. Renowned for their general friendliness, regulars are far from being extinct. But please, support their cause by donating generously to the Poor Boy Foundation
#Thread - A topic started by one member to which anyone can reply. Discussions should be about the original topic.
#PM - Private Message
#IMHO - In my humble opinion, used to express one's meaning

== File downloads in the forums==

An important thing to keep in mind. This is of course, a public space and it behooves you and the health of your computer to take care in clicking on any links/files of unknown origin that someone may post in a thread. Sad as it may seem, there are unsocialized bone nuts out there that get their jollies by causing mayhem. Due to the immediate nature of the forums, we can't insure that a damaging file won't find its way onto the site, though we'll make every effort to keep things safe by removing them ASAP. Please inform the Forum admin or any moderators you see wandering around if you spy something suspicious. Exercise caution and keep your common sense meter turned on and properly calibrated. We cannot be held responsible for the content posted by other Forum users. It may very well happen that something posted, be it text, images, files, or links to any of these thing may be offensive to you. The LAVA moderators will do the best they can to keep the Forums clean of offensive posts, but with such a large community, it is impossible to screen every post quickly and efficiently. Also keep in mind that we highly regard free speech, so the protection of that right will be utmost in deeming what is appropriate. If you have any specific complaint about something offensive you have seen, please feel free to contact a moderator or administrator. The best prevention is sound judgment.

Information about file downloads in the [http://forums.lavag.org/downloads.html Code Repository] can be found [http://forums.lavag.org/Code-Repository-Discussions-f62.html here]:

== The golden forum rules ==

#There will be no excessive use of profanity.
#Do not abuse the PM system
#There will be no racial, ethnic, gender based insults or any other personal discriminations.
#There will be no posts meant to offend or hurt any other member, in a manner which is offensive or inflammatory. Respect new members trying to learn LabVIEW.
#Spamming is not permitted; please keep all your posts as constructive and on-topic as possible.
#Pornography, warez, or any other illegal transactions may NOT be linked in any shape or form.
#All posts are property of the poster. This forum and all web sites owned in conjunction with this forum have the right to request alteration or deletion of any offensive post. Posts may be deleted for any reasons the forum administrators or moderators deem reasonable.
#Users may not argue a moderators decision publicly. Any and all complaints directed at a moderator must first address the moderator in question via PM. If the problem can not be resolved, then the moderator and user must send their positions to the forum admin. The forum admin will make or change any and/or all final decisions.
#Pictures may be posted as long as they are not explicit or offensive.
#Please keep foul language to a minimum, any excessive un-called for language will be removed and you will receive a final warning.
#Remember to post in the correct forum. Take your time to look at other topics and see where your topic should go. If your topic is placed in the wrong forum, it will be moved by a moderator.
#If a topic is recognized as being posted in the wrong forum, or if the post is a violation of our guidelines then please contact a moderator via the "! REPORT" post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a appropriateness of a member's topic will be sent a PM warning and placed into moderation queue upon further actions.
#Having fun is good, we like fun. There are general forums for non-programming related topics. Please keep it positive and polite. We do not censor opinions or ideas on our forums but we do take action against posts and/or topics that could cause unrest in the community beyond a civil and polite disagreement. If you beleive that a post and/or thread fits this critereon then please contact a moderator via the "! REPORT" post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a appropriateness of a member's will be sent a PM warning and placed into moderation queue upon further actions.
#Any impersonation of a user, Admin or moderator, in any mode of communication, is strictly prohibited and will result in a banning.
#Linked and locked topics are pruned regularly to reduce page clutter. If you have a question about where your topic went, please PM (personal message) a Moderator or Administrator before starting a new topic asking where it went, or posting a duplicate of the original topic. We will be happy to provide you with a link to the new location, or a reason why it was locked and/or removed.
#Homework Hustlers are not allowed on the Forums. No exceptions.
#LabVIEW serial number or registration key requests are NOT allowed. No exceptions.

== Penalties for guideline and golden rule violations ==

*Anyone found breaking the above rules and guidelines will have their account suspended for two (2) days.
*Anyone abusing the PM system will have their account suspended for four (4) days.
*If you repeatedly break the rules, your account will be permanently deleted and a ban placed on your registration info to prevent the account from being reused in the future.

All moderator decisions and outcomes (suspensions, deletions etc) will be kept private and confidential. This will allow offenders to recover from what may possibly be a mistake or error on their part or on the part of the moderators.

== Note ==
Only the moderators are authorized by the LAVA Forums to perform any user account suspension/deletion, post editing, post deletion and post moving. In addition, only moderators can decide if a post is a Homework question. Moderators do not read every post. This is impossible. Please use the '''report post to moderator''' button to bring anything to the attention of a moderator.
----

Remember, being a nice netizen will lead to respect, which leads to prompt answers and much fun. Do your best to be cordial, and you will see what a great thing the LabVIEW community is. If you have any questions about any issue brought up by this thread, feel free to ask the moderators, or your fellow Forumites.
Above all, have a nice day

== See also ==
*[http://forums.lavag.org/Tutorials-f72.html Tutorials on Using the Forums]
*[http://forums.lavag.org/Site-Feedback-and-Support-f27.html General Forums Feedback & Support]
*[http://forums.lavag.org/Suggestions-and-Ideas-f67.html Post Suggestions and Ideas for the Forums]
*[http://forums.lavag.org/Bug-Reports-f66.html Report a Forum Bug]

== External links ==
*[http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]

[[category:LAVA]]

Forum Guidelines

2008-12-07T23:34:00Z

Crelf: /* The golden forum rules */

__NOTOC__
{| align="right" border="0"
|__TOC__
|-
|}
== Introduction ==

'''These rules and guidelines apply to the LAVA [http://forums.lavag.org/forums.html Forums] and all the discussion threads associated with the Wiki articles.''' For Guidelines pertaining to other areas of the site see:

*[[LabVIEW Wiki:Policies and guidelines|LabVIEW Wiki Policies and Guidelines]]
*[[Help:Contents|Complete LabVIEW Wiki Help, FAQ and Guidelines]]
*[http://forums.lavag.org/Code-Repository-Discussions-f62.html Code Repository Information and Procedure]

The LAVA Forums are managed and maintained by dedicated LabVIEW enthusiasts like yourself. We are volunteers committed to the development of an open and unbiased exchange of ideas on intermediate to advanced topics in LabVIEW. The document that follows covers key areas of the Forums and should answer most of your questions regarding features, proper usage and etiquette.

== Finding information ==

'''Use Search.''' Your question has probably already been answered. Before posting a LabVIEW question we recommend that you try checking the [[Portal:LabVIEW FAQ|LabVIEW FAQ]] and if your question is still not answered, [http://forums.lavag.org/labviewsearch.html Search the Forums]. A link for searching the Forums can be found in the top header banner at the top right of all pages in the Forums.

== Contributing and posting in the forums ==

*'''Use images'''. Images are the best way to convey the problem you are having. In LabVIEW this is more important because of the graphical nature of the language. You cannot include text code like you would in C++ or other languages. Please check our [http://forums.lavag.org/How-to-Insert-Images-in-your-Posts-t771.html Guide] for how to post images.
*'''Upload example code'''. We love that here. Please upload your code that you are having problems with. You can include all your code into a single [[llb]] or just include all vi's into a *.zip file format. If certain files are missing then it will be more difficult for others to help you with your problem. You will be surprised how many people are willing to re-write your code and make suggestions for you. This can only happen with functional code. Are you uploading code in response to a question? If so then please respect the recipient's LabVIEW version. If you can, perform a save to previous version on your code so they can open it up in their LabVIEW development environment. If the code is very simple and is contained on one diagram then you might want to consider posting an image of the solution instead.
*'''Post in the right Forum'''. Choose a Forum which best suits the topic of your question. For example, questions about user interface issues would best be put in the [http://forums.lavag.org/User-Interface-f19.html user interface Forum], questions about hardware would go in the [http://forums.lavag.org/Hardware-f21.html hardware Forum]. Regardless of which Forum you post in, be detailed. Include as much pertinent information as possible in your question and also include all relevant system specs. Do not respond to a post located in the wrong forum to let the user know it's in the wrong forum. This is the job of the moderator since they have the power to move the post. Again, please use the report post to moderator button. Making comments of this fact is considered impersonating a moderator and is not acceptable.
*'''Update your personal profile''' information to include the current LV version you are using. This will help everyone answer your question properly and tailor it to the proper version you have. Unlike other forums, the number of posts you have does not reflect the experience you have using LV. Please be honest about your experience level. If you are a new user or an experienced professional, this should be reflected by specifying the year you started using LabVIEW in your profile.
*'''Don't cross-post'''. Cross-posting (asking the same question in more than one LAVA Forum) is pretty annoying, so people often ignore cross-posts. Even worse, your question may be deleted by a moderator (mod) or administator (admin). Don't worry, most users check most, if not all of the Forums, so your question will be answered. The reason for this policy is that cross-posts put irrelevant information which takes time to comb through. By avoiding redundant posts, the Forums are kept 'cleaner', thus, it makes it easier to find, and answer questions.
*'''Ask Questions the right way'''. Please help others trying to hep you by providing as much information as possible. Explain what the problem is, what you have done so far, what works, what does not work, etc. Here is an excellent link with more suggestions on [http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]
*'''Be nice to new LabVIEW Users'''. All of us were [http://en.wikipedia.org/wiki/Newbie new] once and many of us still consider ourselves new to LabVIEW even after months (or years) of programming. New LabVIEW users are prospective "Architects" and are therefore our most valuable resource. We must treat new users with kindness and patience — nothing scares potentially valuable contributors away faster than hostility or elitism. please follow the [[#The Golden Forum Rules|Golden Rules]] below for proper conduct. In general, do not post comments to any discussion about how the user will be better off on another website or forum.
*'''Don't abuse the PM''' (Personal Message System) Please don't PM people on these forums for LabVIEW technical support. Especially after you've already posted your question on the Forums. It is a personal choice for someone to respond to a question on the Forums. A PM is Personal (hence the name). Would you go around town knocking on the doors of people you don't know asking for LV help? No, so why would you do the same on the internet? Most of the time, a PM triggers an email notification to the recipient which can be even more annoying. Please think twice before sending a PM. If the person has not responded to your question on the Forums then what makes you think they will respond in person? I think your chances of getting a response from thousands of readers is better than just a response from one.... 'nuf said.
*'''Signature Size'''. Signatures may contain images, however to keep the page loading time and visual annoyance factor down to a minimum, ensure your graphical signatures do not exceed a maximum of 12,500 pixels or 15 kilobytes file size, whichever is reached first. Alternatively, three lines of text can be used as a signature. Do not pad out your text lines with blanks lines. A line of text is defined such that it does not wrap when viewed at a resolution of 640x480. If these limits are exceeded then you may be contacted by a moderator requesting an amendment to your signature. If none is made within a reasonable period of time, then a moderator may remove your signature from your profile.
*'''DON'T WRITE ALL IN CAPS'''. IT CAN BECOME VERY ANNOYING. CAPS ARE GENERALLY REGARDED AS YELLING, SO IF YOU WRITE ALL IN CAPS, FOLKS WILL THINK YOU ARE YELLING AT THEM, SO THEY WILL AVOID YOU. ALSO, CAPS LOOK ugly, so avoid writing all in caps.
*'''No flame wars''' (see glossary below). People obviously don't like to be insulted, so they will avoid flame wars. Flamers get a bad reputation, so their questions are more likely to be ignored.
*'''Spread the Love'''. The regulars would really appreciate it if you would acknowledge the helpfulness of their aid. Not only does praise make them love you, it helps them to understand if their help really was helpful. This way, they will know how to respond if they get a similar question again. This way, they can tailor their responses to better suit your needs.
*'''You may not use profanity'''. It is unprofessional and offensive and will not be tolerated. We have word filters in place for the most vulgar terms. Circumventing those word filters will result in punitive action.
*'''Editing previous posts'''. It is often better to edit than make a new post. Use your better judgment. At the bottom of each of your posts, you will find several icons. Click on the one that says 'Edit' in order to edit a post. You may only edit a post you have written, and there is a 24hr time limit on editions. Here are some general guidelines to follow when editing posts:
**Don't take out anything that may be required to understand the context of later posts
**Edit a previous post rather than make a new one. Use your judgment; sometimes it's necessary to make a new post.
**It's polite to sometimes list what was edited at the bottom of the post. If this ends up being longer than 2 lines, don't bother.
*'''We require all posts to be positive, constructive, and on topic'''. We reserve the right to remove any topics we deem inappropriate or disruptive to the LabVIEW community. Please note that, from time to time, topics may be removed for being inappropriate even though your individual post in that topic may have been perfectly fine. Please do not feel this reflects badly on you.
*'''No Spam'''. Spamming is not permitted; please keep all your posts as constructive and on-topic as possible. If you think a specific post is clearly spam use the report post to moderator button. Replying to such posts only adds visibility to them and makes the problem worse.

== Homework hustlers ==

Homework hustlers are those forum visitors that ask questions on the forums trying to get an easy solution to a school assignment. They do not try to put any effort on their own to solve the school assignment and want other forum members to give them the answer or solution to their problem. Homework Hustlers are not allowed on the Forums. No exceptions.

If you think a certain post is a homework hustling type question. Click on the report post to moderator button. This is the only recourse available to you. DO NOT respond to the post. You are not a moderator and posting negative or disrespectful comments will be considered abuse and results in a penalty by suspension of your account for a period of 2 days (see [[#Penalties for guideline and golden rule violations]]). If a post has been determined to be a Homework question, the guilty party will be contacted via PM and a clarification will be requested. If the issue is still not resolved to the satisfaction of a moderator, then the users' account will be deleted and all their posts removed.

== Glossary of useful forum terms ==

#Admin - (shortened form of Administrator); The ultimate gods of the Forums. They make the final decision on who can be banned, and other life-threatening questions.
#Banned - This is when you are not allowed to make anymore posts. Your IP address, E-mail address, and user name will prevent you to make anymore posts. This is extreeeeemly rare, and is preceded by a warning.
#LabVIEW FAQ - Frequently asked questions. The best resource for common questions.
#Flame war - a deliberate exchange of insults between two parties. This usually involves a series of insulting, irrelevant posts in the same thread.
#Kill - To delete a post.
#LQTM - Laughs Quietly To Myself - similar to, but usually more honest than, LOL (see below).
#LOL - Laughs Out loud.
#RMB - Right menu Button (used in LabVIEW)
#AFAIK - As far as I know
#Nuke - To maliciously destroy a thread.
#Mod - shortened form of Moderator); A moderator who has been given the power to delete/edit other people's posts. They are there to ensure that discussions are relevant and interesting. Don't worry, they only use their powers very sparingly. The moderators were chosen by God himself. God, what with being all-knowing and stuff, chose enough moderators to handle the load. Please don't ask to be made a moderator. We have enough, and you will only be disappointed.
#OCG - Modern, and [http://www.qwantz.com/archive/001057.html slightly crude], interpretation to OMG (see below).
#OMG - Oh My God or Oh My Gosh - an expression of exclaimation.
#Regular - Someone who lives on the Forums. Their diet usually consists of waffles, syrup and Mountain Dew. Renowned for their general friendliness, regulars are far from being extinct. But please, support their cause by donating generously to the Poor Boy Foundation
#Thread - A topic started by one member to which anyone can reply. Discussions should be about the original topic.
#PM - Private Message
#IMHO - In my humble opinion, used to express one's meaning

== File downloads in the forums==

An important thing to keep in mind. This is of course, a public space and it behooves you and the health of your computer to take care in clicking on any links/files of unknown origin that someone may post in a thread. Sad as it may seem, there are unsocialized bone nuts out there that get their jollies by causing mayhem. Due to the immediate nature of the forums, we can't insure that a damaging file won't find its way onto the site, though we'll make every effort to keep things safe by removing them ASAP. Please inform the Forum admin or any moderators you see wandering around if you spy something suspicious. Exercise caution and keep your common sense meter turned on and properly calibrated. We cannot be held responsible for the content posted by other Forum users. It may very well happen that something posted, be it text, images, files, or links to any of these thing may be offensive to you. The LAVA moderators will do the best they can to keep the Forums clean of offensive posts, but with such a large community, it is impossible to screen every post quickly and efficiently. Also keep in mind that we highly regard free speech, so the protection of that right will be utmost in deeming what is appropriate. If you have any specific complaint about something offensive you have seen, please feel free to contact a moderator or administrator. The best prevention is sound judgment.

Information about file downloads in the [http://forums.lavag.org/downloads.html Code Repository] can be found [http://forums.lavag.org/Code-Repository-Discussions-f62.html here]:

== The golden forum rules ==

#There will be no excessive use of profanity.
#Do not abuse the PM system
#There will be no racial, ethnic, gender based insults or any other personal discriminations.
#There will be no posts meant to offend or hurt any other member, in a manner which is offensive or inflammatory. Respect new members trying to learn LabVIEW.
#Spamming is not permitted; please keep all your posts as constructive and on-topic as possible.
#Pornography, warez, or any other illegal transactions may NOT be linked in any shape or form.
#All posts are property of the poster. This forum and all web sites owned in conjunction with this forum have the right to request alteration or deletion of any offensive post. Posts may be deleted for any reasons the forum administrators or moderators deem reasonable.
#Users may not argue a moderators decision publicly. Any and all complaints directed at a moderator must first address the moderator in question via PM. If the problem can not be resolved, then the moderator and user must send their positions to the forum admin. The forum admin will make or change any and/or all final decisions.
#Pictures may be posted as long as they are not explicit or offensive.
#Please keep foul language to a minimum, any excessive un-called for language will be removed and you will receive a final warning.
#Remember to post in the correct forum. Take your time to look at other topics and see where your topic should go. If your topic is placed in the wrong forum, it will be moved by a moderator.
#If a topic is recognized as being posted in the wrong forum, or if the post is a violation of our guidelines then please contact a moderator vai the "! REPORT" post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a member's topic (which has been posted in error and requires locking or moving to another forum) will be sent a PM warning and placed into moderation queue upon further actions.
#Having fun is good, we like fun. There are general forums for non-programming related topics. Please keep it positive and polite. We do not censor opinions or ideas on our forums but we do take action against posts and/or topics that could cause unrest in the community beyond a civil and polite disagreement. If you beleive that a post and/or thread fits this critereon then please contact a moderator via the "! REPORT" post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a member's topic (which has been posted in error and requires locking or moving to another forum) will be sent a PM warning and placed into moderation queue upon further actions.
#Any impersonation of a user, Admin or moderator, in any mode of communication, is strictly prohibited and will result in a banning.
#Linked and locked topics are pruned regularly to reduce page clutter. If you have a question about where your topic went, please PM (personal message) a Moderator or Administrator before starting a new topic asking where it went, or posting a duplicate of the original topic. We will be happy to provide you with a link to the new location, or a reason why it was locked and/or removed.
#Homework Hustlers are not allowed on the Forums. No exceptions.
#LabVIEW serial number or registration key requests are NOT allowed. No exceptions.

== Penalties for guideline and golden rule violations ==

*Anyone found breaking the above rules and guidelines will have their account suspended for two (2) days.
*Anyone abusing the PM system will have their account suspended for four (4) days.
*If you repeatedly break the rules, your account will be permanently deleted and a ban placed on your registration info to prevent the account from being reused in the future.

All moderator decisions and outcomes (suspensions, deletions etc) will be kept private and confidential. This will allow offenders to recover from what may possibly be a mistake or error on their part or on the part of the moderators.

== Note ==
Only the moderators are authorized by the LAVA Forums to perform any user account suspension/deletion, post editing, post deletion and post moving. In addition, only moderators can decide if a post is a Homework question. Moderators do not read every post. This is impossible. Please use the '''report post to moderator''' button to bring anything to the attention of a moderator.
----

Remember, being a nice netizen will lead to respect, which leads to prompt answers and much fun. Do your best to be cordial, and you will see what a great thing the LabVIEW community is. If you have any questions about any issue brought up by this thread, feel free to ask the moderators, or your fellow Forumites.
Above all, have a nice day

== See also ==
*[http://forums.lavag.org/Tutorials-f72.html Tutorials on Using the Forums]
*[http://forums.lavag.org/Site-Feedback-and-Support-f27.html General Forums Feedback & Support]
*[http://forums.lavag.org/Suggestions-and-Ideas-f67.html Post Suggestions and Ideas for the Forums]
*[http://forums.lavag.org/Bug-Reports-f66.html Report a Forum Bug]

== External links ==
*[http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]

[[category:LAVA]]

Forum Guidelines

2008-10-17T17:18:18Z

Crelf: /* Glossary of useful forum terms */

__NOTOC__
{| align="right" border="0"
|__TOC__
|-
|}
== Introduction ==

'''These rules and guidelines apply to the LAVA [http://forums.lavag.org/forums.html Forums] and all the discussion threads associated with the Wiki articles.''' For Guidelines pertaining to other areas of the site see:

*[[LabVIEW Wiki:Policies and guidelines|LabVIEW Wiki Policies and Guidelines]]
*[[Help:Contents|Complete LabVIEW Wiki Help, FAQ and Guidelines]]
*[http://forums.lavag.org/Code-Repository-Discussions-f62.html Code Repository Information and Procedure]

The LAVA Forums are managed and maintained by dedicated LabVIEW enthusiasts like yourself. We are volunteers committed to the development of an open and unbiased exchange of ideas on intermediate to advanced topics in LabVIEW. The document that follows covers key areas of the Forums and should answer most of your questions regarding features, proper usage and etiquette.

== Finding information ==

'''Use Search.''' Your question has probably already been answered. Before posting a LabVIEW question we recommend that you try checking the [[Portal:LabVIEW FAQ|LabVIEW FAQ]] and if your question is still not answered, [http://forums.lavag.org/labviewsearch.html Search the Forums]. A link for searching the Forums can be found in the top header banner at the top right of all pages in the Forums.

== Contributing and posting in the forums ==

*'''Use images'''. Images are the best way to convey the problem you are having. In LabVIEW this is more important because of the graphical nature of the language. You cannot include text code like you would in C++ or other languages. Please check our [http://forums.lavag.org/How-to-Insert-Images-in-your-Posts-t771.html Guide] for how to post images.
*'''Upload example code'''. We love that here. Please upload your code that you are having problems with. You can include all your code into a single [[llb]] or just include all vi's into a *.zip file format. If certain files are missing then it will be more difficult for others to help you with your problem. You will be surprised how many people are willing to re-write your code and make suggestions for you. This can only happen with functional code. Are you uploading code in response to a question? If so then please respect the recipient's LabVIEW version. If you can, perform a save to previous version on your code so they can open it up in their LabVIEW development environment. If the code is very simple and is contained on one diagram then you might want to consider posting an image of the solution instead.
*'''Post in the right Forum'''. Choose a Forum which best suits the topic of your question. For example, questions about user interface issues would best be put in the [http://forums.lavag.org/User-Interface-f19.html user interface Forum], questions about hardware would go in the [http://forums.lavag.org/Hardware-f21.html hardware Forum]. Regardless of which Forum you post in, be detailed. Include as much pertinent information as possible in your question and also include all relevant system specs. Do not respond to a post located in the wrong forum to let the user know it's in the wrong forum. This is the job of the moderator since they have the power to move the post. Again, please use the report post to moderator button. Making comments of this fact is considered impersonating a moderator and is not acceptable.
*'''Update your personal profile''' information to include the current LV version you are using. This will help everyone answer your question properly and tailor it to the proper version you have. Unlike other forums, the number of posts you have does not reflect the experience you have using LV. Please be honest about your experience level. If you are a new user or an experienced professional, this should be reflected by specifying the year you started using LabVIEW in your profile.
*'''Don't cross-post'''. Cross-posting (asking the same question in more than one LAVA Forum) is pretty annoying, so people often ignore cross-posts. Even worse, your question may be deleted by a moderator (mod) or administator (admin). Don't worry, most users check most, if not all of the Forums, so your question will be answered. The reason for this policy is that cross-posts put irrelevant information which takes time to comb through. By avoiding redundant posts, the Forums are kept 'cleaner', thus, it makes it easier to find, and answer questions.
*'''Ask Questions the right way'''. Please help others trying to hep you by providing as much information as possible. Explain what the problem is, what you have done so far, what works, what does not work, etc. Here is an excellent link with more suggestions on [http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]
*'''Be nice to new LabVIEW Users'''. All of us were [http://en.wikipedia.org/wiki/Newbie new] once and many of us still consider ourselves new to LabVIEW even after months (or years) of programming. New LabVIEW users are prospective "Architects" and are therefore our most valuable resource. We must treat new users with kindness and patience — nothing scares potentially valuable contributors away faster than hostility or elitism. please follow the [[#The Golden Forum Rules|Golden Rules]] below for proper conduct. In general, do not post comments to any discussion about how the user will be better off on another website or forum.
*'''Don't abuse the PM''' (Personal Message System) Please don't PM people on these forums for LabVIEW technical support. Especially after you've already posted your question on the Forums. It is a personal choice for someone to respond to a question on the Forums. A PM is Personal (hence the name). Would you go around town knocking on the doors of people you don't know asking for LV help? No, so why would you do the same on the internet? Most of the time, a PM triggers an email notification to the recipient which can be even more annoying. Please think twice before sending a PM. If the person has not responded to your question on the Forums then what makes you think they will respond in person? I think your chances of getting a response from thousands of readers is better than just a response from one.... 'nuf said.
*'''Signature Size'''. Signatures may contain images, however to keep the page loading time and visual annoyance factor down to a minimum, ensure your graphical signatures do not exceed a maximum of 12,500 pixels or 15 kilobytes file size, whichever is reached first. Alternatively, three lines of text can be used as a signature. Do not pad out your text lines with blanks lines. A line of text is defined such that it does not wrap when viewed at a resolution of 640x480. If these limits are exceeded then you may be contacted by a moderator requesting an amendment to your signature. If none is made within a reasonable period of time, then a moderator may remove your signature from your profile.
*'''DON'T WRITE ALL IN CAPS'''. IT CAN BECOME VERY ANNOYING. CAPS ARE GENERALLY REGARDED AS YELLING, SO IF YOU WRITE ALL IN CAPS, FOLKS WILL THINK YOU ARE YELLING AT THEM, SO THEY WILL AVOID YOU. ALSO, CAPS LOOK ugly, so avoid writing all in caps.
*'''No flame wars''' (see glossary below). People obviously don't like to be insulted, so they will avoid flame wars. Flamers get a bad reputation, so their questions are more likely to be ignored.
*'''Spread the Love'''. The regulars would really appreciate it if you would acknowledge the helpfulness of their aid. Not only does praise make them love you, it helps them to understand if their help really was helpful. This way, they will know how to respond if they get a similar question again. This way, they can tailor their responses to better suit your needs.
*'''You may not use profanity'''. It is unprofessional and offensive and will not be tolerated. We have word filters in place for the most vulgar terms. Circumventing those word filters will result in punitive action.
*'''Editing previous posts'''. It is often better to edit than make a new post. Use your better judgment. At the bottom of each of your posts, you will find several icons. Click on the one that says 'Edit' in order to edit a post. You may only edit a post you have written, and there is a 24hr time limit on editions. Here are some general guidelines to follow when editing posts:
**Don't take out anything that may be required to understand the context of later posts
**Edit a previous post rather than make a new one. Use your judgment; sometimes it's necessary to make a new post.
**It's polite to sometimes list what was edited at the bottom of the post. If this ends up being longer than 2 lines, don't bother.
*'''We require all posts to be positive, constructive, and on topic'''. We reserve the right to remove any topics we deem inappropriate or disruptive to the LabVIEW community. Please note that, from time to time, topics may be removed for being inappropriate even though your individual post in that topic may have been perfectly fine. Please do not feel this reflects badly on you.
*'''No Spam'''. Spamming is not permitted; please keep all your posts as constructive and on-topic as possible. If you think a specific post is clearly spam use the report post to moderator button. Replying to such posts only adds visibility to them and makes the problem worse.

== Homework hustlers ==

Homework hustlers are those forum visitors that ask questions on the forums trying to get an easy solution to a school assignment. They do not try to put any effort on their own to solve the school assignment and want other forum members to give them the answer or solution to their problem. Homework Hustlers are not allowed on the Forums. No exceptions.

If you think a certain post is a homework hustling type question. Click on the report post to moderator button. This is the only recourse available to you. DO NOT respond to the post. You are not a moderator and posting negative or disrespectful comments will be considered abuse and results in a penalty by suspension of your account for a period of 2 days (see [[#Penalties for guideline and golden rule violations]]). If a post has been determined to be a Homework question, the guilty party will be contacted via PM and a clarification will be requested. If the issue is still not resolved to the satisfaction of a moderator, then the users' account will be deleted and all their posts removed.

== Glossary of useful forum terms ==

#Admin - (shortened form of Administrator); The ultimate gods of the Forums. They make the final decision on who can be banned, and other life-threatening questions.
#Banned - This is when you are not allowed to make anymore posts. Your IP address, E-mail address, and user name will prevent you to make anymore posts. This is extreeeeemly rare, and is preceded by a warning.
#LabVIEW FAQ - Frequently asked questions. The best resource for common questions.
#Flame war - a deliberate exchange of insults between two parties. This usually involves a series of insulting, irrelevant posts in the same thread.
#Kill - To delete a post.
#LQTM - Laughs Quietly To Myself - similar to, but usually more honest than, LOL (see below).
#LOL - Laughs Out loud.
#RMB - Right menu Button (used in LabVIEW)
#AFAIK - As far as I know
#Nuke - To maliciously destroy a thread.
#Mod - shortened form of Moderator); A moderator who has been given the power to delete/edit other people's posts. They are there to ensure that discussions are relevant and interesting. Don't worry, they only use their powers very sparingly. The moderators were chosen by God himself. God, what with being all-knowing and stuff, chose enough moderators to handle the load. Please don't ask to be made a moderator. We have enough, and you will only be disappointed.
#OCG - Modern, and [http://www.qwantz.com/archive/001057.html slightly crude], interpretation to OMG (see below).
#OMG - Oh My God or Oh My Gosh - an expression of exclaimation.
#Regular - Someone who lives on the Forums. Their diet usually consists of waffles, syrup and Mountain Dew. Renowned for their general friendliness, regulars are far from being extinct. But please, support their cause by donating generously to the Poor Boy Foundation
#Thread - A topic started by one member to which anyone can reply. Discussions should be about the original topic.
#PM - Private Message
#IMHO - In my humble opinion, used to express one's meaning

== File downloads in the forums==

An important thing to keep in mind. This is of course, a public space and it behooves you and the health of your computer to take care in clicking on any links/files of unknown origin that someone may post in a thread. Sad as it may seem, there are unsocialized bone nuts out there that get their jollies by causing mayhem. Due to the immediate nature of the forums, we can't insure that a damaging file won't find its way onto the site, though we'll make every effort to keep things safe by removing them ASAP. Please inform the Forum admin or any moderators you see wandering around if you spy something suspicious. Exercise caution and keep your common sense meter turned on and properly calibrated. We cannot be held responsible for the content posted by other Forum users. It may very well happen that something posted, be it text, images, files, or links to any of these thing may be offensive to you. The LAVA moderators will do the best they can to keep the Forums clean of offensive posts, but with such a large community, it is impossible to screen every post quickly and efficiently. Also keep in mind that we highly regard free speech, so the protection of that right will be utmost in deeming what is appropriate. If you have any specific complaint about something offensive you have seen, please feel free to contact a moderator or administrator. The best prevention is sound judgment.

Information about file downloads in the [http://forums.lavag.org/downloads.html Code Repository] can be found [http://forums.lavag.org/Code-Repository-Discussions-f62.html here]:

== The golden forum rules ==

#There will be no excessive use of profanity.
#Do not abuse the PM system
#There will be no racial, ethnic, gender based insults or any other personal discriminations.
#There will be no posts meant to offend or hurt any other member, in a manner which is offensive or inflammatory. Respect new members trying to learn LabVIEW.
#Spamming is not permitted; please keep all your posts as constructive and on-topic as possible.
#Pornography, warez, or any other illegal transactions may NOT be linked in any shape or form.
#All posts are property of the poster. This forum and all web sites owned in conjunction with this forum have the right to request alteration or deletion of any offensive post. Posts may be deleted for any reasons the forum administrators or moderators deem reasonable.
#Users may not argue a moderators decision publicly. Any and all complaints directed at a moderator must first address the moderator in question via PM. If the problem can not be resolved, then the moderator and user must send their positions to the forum admin. The forum admin will make or change any and/or all final decisions.
#Pictures may be posted as long as they are not explicit or offensive.
#Please keep foul language to a minimum, any excessive un-called for language will be removed and you will receive a final warning.
#Remember to post in the correct forum. Take your time to look at other topics and see where your topic should go. If your topic is placed in the wrong forum, it will be moved by a moderator.
#If a topic is recognized as being posted in the wrong forum, or if the post is a violation of our guidelines then please contact a moderator either via PM (personal message) or the report post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a member's topic (which has been posted in error and requires locking or moving to another forum) will be sent a PM warning and placed into moderation queue upon further actions.
#Having fun is good, we like fun. There are general forums for non-programming related topics. Please keep it positive and polite. We do not censor opinions or ideas on our forums but we do take action against posts and/or topics that could cause unrest in the community beyond a civil and polite disagreement.
#Any impersonation of a user, Admin or moderator, in any mode of communication, is strictly prohibited and will result in a banning.
#Linked and locked topics are pruned regularly to reduce page clutter. If you have a question about where your topic went, please PM (personal message) a Moderator or Administrator before starting a new topic asking where it went, or posting a duplicate of the original topic. We will be happy to provide you with a link to the new location, or a reason why it was locked and/or removed.
#Homework Hustlers are not allowed on the Forums. No exceptions.
#LabVIEW serial number or registration key requests are NOT allowed. No exceptions.

== Penalties for guideline and golden rule violations ==

*Anyone found breaking the above rules and guidelines will have their account suspended for two (2) days.
*Anyone abusing the PM system will have their account suspended for four (4) days.
*If you repeatedly break the rules, your account will be permanently deleted and a ban placed on your registration info to prevent the account from being reused in the future.

All moderator decisions and outcomes (suspensions, deletions etc) will be kept private and confidential. This will allow offenders to recover from what may possibly be a mistake or error on their part or on the part of the moderators.

== Note ==
Only the moderators are authorized by the LAVA Forums to perform any user account suspension/deletion, post editing, post deletion and post moving. In addition, only moderators can decide if a post is a Homework question. Moderators do not read every post. This is impossible. Please use the '''report post to moderator''' button to bring anything to the attention of a moderator.
----

Remember, being a nice netizen will lead to respect, which leads to prompt answers and much fun. Do your best to be cordial, and you will see what a great thing the LabVIEW community is. If you have any questions about any issue brought up by this thread, feel free to ask the moderators, or your fellow Forumites.
Above all, have a nice day

== See also ==
*[http://forums.lavag.org/Tutorials-f72.html Tutorials on Using the Forums]
*[http://forums.lavag.org/Site-Feedback-and-Support-f27.html General Forums Feedback & Support]
*[http://forums.lavag.org/Suggestions-and-Ideas-f67.html Post Suggestions and Ideas for the Forums]
*[http://forums.lavag.org/Bug-Reports-f66.html Report a Forum Bug]

== External links ==
*[http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]

[[category:LAVA]]

Forum Guidelines

2008-10-17T16:26:39Z

Crelf: /* Glossary of useful forum terms */

__NOTOC__
{| align="right" border="0"
|__TOC__
|-
|}
== Introduction ==

'''These rules and guidelines apply to the LAVA [http://forums.lavag.org/forums.html Forums] and all the discussion threads associated with the Wiki articles.''' For Guidelines pertaining to other areas of the site see:

*[[LabVIEW Wiki:Policies and guidelines|LabVIEW Wiki Policies and Guidelines]]
*[[Help:Contents|Complete LabVIEW Wiki Help, FAQ and Guidelines]]
*[http://forums.lavag.org/Code-Repository-Discussions-f62.html Code Repository Information and Procedure]

The LAVA Forums are managed and maintained by dedicated LabVIEW enthusiasts like yourself. We are volunteers committed to the development of an open and unbiased exchange of ideas on intermediate to advanced topics in LabVIEW. The document that follows covers key areas of the Forums and should answer most of your questions regarding features, proper usage and etiquette.

== Finding information ==

'''Use Search.''' Your question has probably already been answered. Before posting a LabVIEW question we recommend that you try checking the [[Portal:LabVIEW FAQ|LabVIEW FAQ]] and if your question is still not answered, [http://forums.lavag.org/labviewsearch.html Search the Forums]. A link for searching the Forums can be found in the top header banner at the top right of all pages in the Forums.

== Contributing and posting in the forums ==

*'''Use images'''. Images are the best way to convey the problem you are having. In LabVIEW this is more important because of the graphical nature of the language. You cannot include text code like you would in C++ or other languages. Please check our [http://forums.lavag.org/How-to-Insert-Images-in-your-Posts-t771.html Guide] for how to post images.
*'''Upload example code'''. We love that here. Please upload your code that you are having problems with. You can include all your code into a single [[llb]] or just include all vi's into a *.zip file format. If certain files are missing then it will be more difficult for others to help you with your problem. You will be surprised how many people are willing to re-write your code and make suggestions for you. This can only happen with functional code. Are you uploading code in response to a question? If so then please respect the recipient's LabVIEW version. If you can, perform a save to previous version on your code so they can open it up in their LabVIEW development environment. If the code is very simple and is contained on one diagram then you might want to consider posting an image of the solution instead.
*'''Post in the right Forum'''. Choose a Forum which best suits the topic of your question. For example, questions about user interface issues would best be put in the [http://forums.lavag.org/User-Interface-f19.html user interface Forum], questions about hardware would go in the [http://forums.lavag.org/Hardware-f21.html hardware Forum]. Regardless of which Forum you post in, be detailed. Include as much pertinent information as possible in your question and also include all relevant system specs. Do not respond to a post located in the wrong forum to let the user know it's in the wrong forum. This is the job of the moderator since they have the power to move the post. Again, please use the report post to moderator button. Making comments of this fact is considered impersonating a moderator and is not acceptable.
*'''Update your personal profile''' information to include the current LV version you are using. This will help everyone answer your question properly and tailor it to the proper version you have. Unlike other forums, the number of posts you have does not reflect the experience you have using LV. Please be honest about your experience level. If you are a new user or an experienced professional, this should be reflected by specifying the year you started using LabVIEW in your profile.
*'''Don't cross-post'''. Cross-posting (asking the same question in more than one LAVA Forum) is pretty annoying, so people often ignore cross-posts. Even worse, your question may be deleted by a moderator (mod) or administator (admin). Don't worry, most users check most, if not all of the Forums, so your question will be answered. The reason for this policy is that cross-posts put irrelevant information which takes time to comb through. By avoiding redundant posts, the Forums are kept 'cleaner', thus, it makes it easier to find, and answer questions.
*'''Ask Questions the right way'''. Please help others trying to hep you by providing as much information as possible. Explain what the problem is, what you have done so far, what works, what does not work, etc. Here is an excellent link with more suggestions on [http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]
*'''Be nice to new LabVIEW Users'''. All of us were [http://en.wikipedia.org/wiki/Newbie new] once and many of us still consider ourselves new to LabVIEW even after months (or years) of programming. New LabVIEW users are prospective "Architects" and are therefore our most valuable resource. We must treat new users with kindness and patience — nothing scares potentially valuable contributors away faster than hostility or elitism. please follow the [[#The Golden Forum Rules|Golden Rules]] below for proper conduct. In general, do not post comments to any discussion about how the user will be better off on another website or forum.
*'''Don't abuse the PM''' (Personal Message System) Please don't PM people on these forums for LabVIEW technical support. Especially after you've already posted your question on the Forums. It is a personal choice for someone to respond to a question on the Forums. A PM is Personal (hence the name). Would you go around town knocking on the doors of people you don't know asking for LV help? No, so why would you do the same on the internet? Most of the time, a PM triggers an email notification to the recipient which can be even more annoying. Please think twice before sending a PM. If the person has not responded to your question on the Forums then what makes you think they will respond in person? I think your chances of getting a response from thousands of readers is better than just a response from one.... 'nuf said.
*'''Signature Size'''. Signatures may contain images, however to keep the page loading time and visual annoyance factor down to a minimum, ensure your graphical signatures do not exceed a maximum of 12,500 pixels or 15 kilobytes file size, whichever is reached first. Alternatively, three lines of text can be used as a signature. Do not pad out your text lines with blanks lines. A line of text is defined such that it does not wrap when viewed at a resolution of 640x480. If these limits are exceeded then you may be contacted by a moderator requesting an amendment to your signature. If none is made within a reasonable period of time, then a moderator may remove your signature from your profile.
*'''DON'T WRITE ALL IN CAPS'''. IT CAN BECOME VERY ANNOYING. CAPS ARE GENERALLY REGARDED AS YELLING, SO IF YOU WRITE ALL IN CAPS, FOLKS WILL THINK YOU ARE YELLING AT THEM, SO THEY WILL AVOID YOU. ALSO, CAPS LOOK ugly, so avoid writing all in caps.
*'''No flame wars''' (see glossary below). People obviously don't like to be insulted, so they will avoid flame wars. Flamers get a bad reputation, so their questions are more likely to be ignored.
*'''Spread the Love'''. The regulars would really appreciate it if you would acknowledge the helpfulness of their aid. Not only does praise make them love you, it helps them to understand if their help really was helpful. This way, they will know how to respond if they get a similar question again. This way, they can tailor their responses to better suit your needs.
*'''You may not use profanity'''. It is unprofessional and offensive and will not be tolerated. We have word filters in place for the most vulgar terms. Circumventing those word filters will result in punitive action.
*'''Editing previous posts'''. It is often better to edit than make a new post. Use your better judgment. At the bottom of each of your posts, you will find several icons. Click on the one that says 'Edit' in order to edit a post. You may only edit a post you have written, and there is a 24hr time limit on editions. Here are some general guidelines to follow when editing posts:
**Don't take out anything that may be required to understand the context of later posts
**Edit a previous post rather than make a new one. Use your judgment; sometimes it's necessary to make a new post.
**It's polite to sometimes list what was edited at the bottom of the post. If this ends up being longer than 2 lines, don't bother.
*'''We require all posts to be positive, constructive, and on topic'''. We reserve the right to remove any topics we deem inappropriate or disruptive to the LabVIEW community. Please note that, from time to time, topics may be removed for being inappropriate even though your individual post in that topic may have been perfectly fine. Please do not feel this reflects badly on you.
*'''No Spam'''. Spamming is not permitted; please keep all your posts as constructive and on-topic as possible. If you think a specific post is clearly spam use the report post to moderator button. Replying to such posts only adds visibility to them and makes the problem worse.

== Homework hustlers ==

Homework hustlers are those forum visitors that ask questions on the forums trying to get an easy solution to a school assignment. They do not try to put any effort on their own to solve the school assignment and want other forum members to give them the answer or solution to their problem. Homework Hustlers are not allowed on the Forums. No exceptions.

If you think a certain post is a homework hustling type question. Click on the report post to moderator button. This is the only recourse available to you. DO NOT respond to the post. You are not a moderator and posting negative or disrespectful comments will be considered abuse and results in a penalty by suspension of your account for a period of 2 days (see [[#Penalties for guideline and golden rule violations]]). If a post has been determined to be a Homework question, the guilty party will be contacted via PM and a clarification will be requested. If the issue is still not resolved to the satisfaction of a moderator, then the users' account will be deleted and all their posts removed.

== Glossary of useful forum terms ==

#Admin - (shortened form of Administrator); The ultimate gods of the Forums. They make the final decision on who can be banned, and other life-threatening questions.
#Banned - This is when you are not allowed to make anymore posts. Your IP address, E-mail address, and user name will prevent you to make anymore posts. This is extreeeeemly rare, and is preceded by a warning.
#LabVIEW FAQ - Frequently asked questions. The best resource for common questions.
#Flame war - a deliberate exchange of insults between two parties. This usually involves a series of insulting, irrelevant posts in the same thread.
#Kill - To delete a post.
#LQTM - Laughs Quietly To Myself - similar to, but usually more honest than, LOL (see below).
#LOL - Laughs Out loud.
#RMB - Right menu Button (used in LabVIEW)
#AFAIK - As far as I know
#Nuke - To maliciously destroy a thread.
#Mod - shortened form of Moderator); A moderator who has been given the power to delete/edit other people's posts. They are there to ensure that discussions are relevant and interesting. Don't worry, they only use their powers very sparingly. The moderators were chosen by God himself. God, what with being all-knowing and stuff, chose enough moderators to handle the load. Please don't ask to be made a moderator. We have enough, and you will only be disappointed.
#OCG - Modern, and [http://www.boingboing.net/2008/04/23/graphic-graphic-uk-o.html slightly crude], interpretation to OMG (see below).
#OMG - Oh My God or Oh My Gosh - an expression of exclaimation.
#Regular - Someone who lives on the Forums. Their diet usually consists of waffles, syrup and Mountain Dew. Renowned for their general friendliness, regulars are far from being extinct. But please, support their cause by donating generously to the Poor Boy Foundation
#Thread - A topic started by one member to which anyone can reply. Discussions should be about the original topic.
#PM - Private Message
#IMHO - In my humble opinion, used to express one's meaning

== File downloads in the forums==

An important thing to keep in mind. This is of course, a public space and it behooves you and the health of your computer to take care in clicking on any links/files of unknown origin that someone may post in a thread. Sad as it may seem, there are unsocialized bone nuts out there that get their jollies by causing mayhem. Due to the immediate nature of the forums, we can't insure that a damaging file won't find its way onto the site, though we'll make every effort to keep things safe by removing them ASAP. Please inform the Forum admin or any moderators you see wandering around if you spy something suspicious. Exercise caution and keep your common sense meter turned on and properly calibrated. We cannot be held responsible for the content posted by other Forum users. It may very well happen that something posted, be it text, images, files, or links to any of these thing may be offensive to you. The LAVA moderators will do the best they can to keep the Forums clean of offensive posts, but with such a large community, it is impossible to screen every post quickly and efficiently. Also keep in mind that we highly regard free speech, so the protection of that right will be utmost in deeming what is appropriate. If you have any specific complaint about something offensive you have seen, please feel free to contact a moderator or administrator. The best prevention is sound judgment.

Information about file downloads in the [http://forums.lavag.org/downloads.html Code Repository] can be found [http://forums.lavag.org/Code-Repository-Discussions-f62.html here]:

== The golden forum rules ==

#There will be no excessive use of profanity.
#Do not abuse the PM system
#There will be no racial, ethnic, gender based insults or any other personal discriminations.
#There will be no posts meant to offend or hurt any other member, in a manner which is offensive or inflammatory. Respect new members trying to learn LabVIEW.
#Spamming is not permitted; please keep all your posts as constructive and on-topic as possible.
#Pornography, warez, or any other illegal transactions may NOT be linked in any shape or form.
#All posts are property of the poster. This forum and all web sites owned in conjunction with this forum have the right to request alteration or deletion of any offensive post. Posts may be deleted for any reasons the forum administrators or moderators deem reasonable.
#Users may not argue a moderators decision publicly. Any and all complaints directed at a moderator must first address the moderator in question via PM. If the problem can not be resolved, then the moderator and user must send their positions to the forum admin. The forum admin will make or change any and/or all final decisions.
#Pictures may be posted as long as they are not explicit or offensive.
#Please keep foul language to a minimum, any excessive un-called for language will be removed and you will receive a final warning.
#Remember to post in the correct forum. Take your time to look at other topics and see where your topic should go. If your topic is placed in the wrong forum, it will be moved by a moderator.
#If a topic is recognized as being posted in the wrong forum, or if the post is a violation of our guidelines then please contact a moderator either via PM (personal message) or the report post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a member's topic (which has been posted in error and requires locking or moving to another forum) will be sent a PM warning and placed into moderation queue upon further actions.
#Having fun is good, we like fun. There are general forums for non-programming related topics. Please keep it positive and polite. We do not censor opinions or ideas on our forums but we do take action against posts and/or topics that could cause unrest in the community beyond a civil and polite disagreement.
#Any impersonation of a user, Admin or moderator, in any mode of communication, is strictly prohibited and will result in a banning.
#Linked and locked topics are pruned regularly to reduce page clutter. If you have a question about where your topic went, please PM (personal message) a Moderator or Administrator before starting a new topic asking where it went, or posting a duplicate of the original topic. We will be happy to provide you with a link to the new location, or a reason why it was locked and/or removed.
#Homework Hustlers are not allowed on the Forums. No exceptions.
#LabVIEW serial number or registration key requests are NOT allowed. No exceptions.

== Penalties for guideline and golden rule violations ==

*Anyone found breaking the above rules and guidelines will have their account suspended for two (2) days.
*Anyone abusing the PM system will have their account suspended for four (4) days.
*If you repeatedly break the rules, your account will be permanently deleted and a ban placed on your registration info to prevent the account from being reused in the future.

All moderator decisions and outcomes (suspensions, deletions etc) will be kept private and confidential. This will allow offenders to recover from what may possibly be a mistake or error on their part or on the part of the moderators.

== Note ==
Only the moderators are authorized by the LAVA Forums to perform any user account suspension/deletion, post editing, post deletion and post moving. In addition, only moderators can decide if a post is a Homework question. Moderators do not read every post. This is impossible. Please use the '''report post to moderator''' button to bring anything to the attention of a moderator.
----

Remember, being a nice netizen will lead to respect, which leads to prompt answers and much fun. Do your best to be cordial, and you will see what a great thing the LabVIEW community is. If you have any questions about any issue brought up by this thread, feel free to ask the moderators, or your fellow Forumites.
Above all, have a nice day

== See also ==
*[http://forums.lavag.org/Tutorials-f72.html Tutorials on Using the Forums]
*[http://forums.lavag.org/Site-Feedback-and-Support-f27.html General Forums Feedback & Support]
*[http://forums.lavag.org/Suggestions-and-Ideas-f67.html Post Suggestions and Ideas for the Forums]
*[http://forums.lavag.org/Bug-Reports-f66.html Report a Forum Bug]

== External links ==
*[http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]

[[category:LAVA]]

Forum Guidelines

2008-10-17T16:22:41Z

Crelf: /* Glossary of useful forum terms */

__NOTOC__
{| align="right" border="0"
|__TOC__
|-
|}
== Introduction ==

'''These rules and guidelines apply to the LAVA [http://forums.lavag.org/forums.html Forums] and all the discussion threads associated with the Wiki articles.''' For Guidelines pertaining to other areas of the site see:

*[[LabVIEW Wiki:Policies and guidelines|LabVIEW Wiki Policies and Guidelines]]
*[[Help:Contents|Complete LabVIEW Wiki Help, FAQ and Guidelines]]
*[http://forums.lavag.org/Code-Repository-Discussions-f62.html Code Repository Information and Procedure]

The LAVA Forums are managed and maintained by dedicated LabVIEW enthusiasts like yourself. We are volunteers committed to the development of an open and unbiased exchange of ideas on intermediate to advanced topics in LabVIEW. The document that follows covers key areas of the Forums and should answer most of your questions regarding features, proper usage and etiquette.

== Finding information ==

'''Use Search.''' Your question has probably already been answered. Before posting a LabVIEW question we recommend that you try checking the [[Portal:LabVIEW FAQ|LabVIEW FAQ]] and if your question is still not answered, [http://forums.lavag.org/labviewsearch.html Search the Forums]. A link for searching the Forums can be found in the top header banner at the top right of all pages in the Forums.

== Contributing and posting in the forums ==

*'''Use images'''. Images are the best way to convey the problem you are having. In LabVIEW this is more important because of the graphical nature of the language. You cannot include text code like you would in C++ or other languages. Please check our [http://forums.lavag.org/How-to-Insert-Images-in-your-Posts-t771.html Guide] for how to post images.
*'''Upload example code'''. We love that here. Please upload your code that you are having problems with. You can include all your code into a single [[llb]] or just include all vi's into a *.zip file format. If certain files are missing then it will be more difficult for others to help you with your problem. You will be surprised how many people are willing to re-write your code and make suggestions for you. This can only happen with functional code. Are you uploading code in response to a question? If so then please respect the recipient's LabVIEW version. If you can, perform a save to previous version on your code so they can open it up in their LabVIEW development environment. If the code is very simple and is contained on one diagram then you might want to consider posting an image of the solution instead.
*'''Post in the right Forum'''. Choose a Forum which best suits the topic of your question. For example, questions about user interface issues would best be put in the [http://forums.lavag.org/User-Interface-f19.html user interface Forum], questions about hardware would go in the [http://forums.lavag.org/Hardware-f21.html hardware Forum]. Regardless of which Forum you post in, be detailed. Include as much pertinent information as possible in your question and also include all relevant system specs. Do not respond to a post located in the wrong forum to let the user know it's in the wrong forum. This is the job of the moderator since they have the power to move the post. Again, please use the report post to moderator button. Making comments of this fact is considered impersonating a moderator and is not acceptable.
*'''Update your personal profile''' information to include the current LV version you are using. This will help everyone answer your question properly and tailor it to the proper version you have. Unlike other forums, the number of posts you have does not reflect the experience you have using LV. Please be honest about your experience level. If you are a new user or an experienced professional, this should be reflected by specifying the year you started using LabVIEW in your profile.
*'''Don't cross-post'''. Cross-posting (asking the same question in more than one LAVA Forum) is pretty annoying, so people often ignore cross-posts. Even worse, your question may be deleted by a moderator (mod) or administator (admin). Don't worry, most users check most, if not all of the Forums, so your question will be answered. The reason for this policy is that cross-posts put irrelevant information which takes time to comb through. By avoiding redundant posts, the Forums are kept 'cleaner', thus, it makes it easier to find, and answer questions.
*'''Ask Questions the right way'''. Please help others trying to hep you by providing as much information as possible. Explain what the problem is, what you have done so far, what works, what does not work, etc. Here is an excellent link with more suggestions on [http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]
*'''Be nice to new LabVIEW Users'''. All of us were [http://en.wikipedia.org/wiki/Newbie new] once and many of us still consider ourselves new to LabVIEW even after months (or years) of programming. New LabVIEW users are prospective "Architects" and are therefore our most valuable resource. We must treat new users with kindness and patience — nothing scares potentially valuable contributors away faster than hostility or elitism. please follow the [[#The Golden Forum Rules|Golden Rules]] below for proper conduct. In general, do not post comments to any discussion about how the user will be better off on another website or forum.
*'''Don't abuse the PM''' (Personal Message System) Please don't PM people on these forums for LabVIEW technical support. Especially after you've already posted your question on the Forums. It is a personal choice for someone to respond to a question on the Forums. A PM is Personal (hence the name). Would you go around town knocking on the doors of people you don't know asking for LV help? No, so why would you do the same on the internet? Most of the time, a PM triggers an email notification to the recipient which can be even more annoying. Please think twice before sending a PM. If the person has not responded to your question on the Forums then what makes you think they will respond in person? I think your chances of getting a response from thousands of readers is better than just a response from one.... 'nuf said.
*'''Signature Size'''. Signatures may contain images, however to keep the page loading time and visual annoyance factor down to a minimum, ensure your graphical signatures do not exceed a maximum of 12,500 pixels or 15 kilobytes file size, whichever is reached first. Alternatively, three lines of text can be used as a signature. Do not pad out your text lines with blanks lines. A line of text is defined such that it does not wrap when viewed at a resolution of 640x480. If these limits are exceeded then you may be contacted by a moderator requesting an amendment to your signature. If none is made within a reasonable period of time, then a moderator may remove your signature from your profile.
*'''DON'T WRITE ALL IN CAPS'''. IT CAN BECOME VERY ANNOYING. CAPS ARE GENERALLY REGARDED AS YELLING, SO IF YOU WRITE ALL IN CAPS, FOLKS WILL THINK YOU ARE YELLING AT THEM, SO THEY WILL AVOID YOU. ALSO, CAPS LOOK ugly, so avoid writing all in caps.
*'''No flame wars''' (see glossary below). People obviously don't like to be insulted, so they will avoid flame wars. Flamers get a bad reputation, so their questions are more likely to be ignored.
*'''Spread the Love'''. The regulars would really appreciate it if you would acknowledge the helpfulness of their aid. Not only does praise make them love you, it helps them to understand if their help really was helpful. This way, they will know how to respond if they get a similar question again. This way, they can tailor their responses to better suit your needs.
*'''You may not use profanity'''. It is unprofessional and offensive and will not be tolerated. We have word filters in place for the most vulgar terms. Circumventing those word filters will result in punitive action.
*'''Editing previous posts'''. It is often better to edit than make a new post. Use your better judgment. At the bottom of each of your posts, you will find several icons. Click on the one that says 'Edit' in order to edit a post. You may only edit a post you have written, and there is a 24hr time limit on editions. Here are some general guidelines to follow when editing posts:
**Don't take out anything that may be required to understand the context of later posts
**Edit a previous post rather than make a new one. Use your judgment; sometimes it's necessary to make a new post.
**It's polite to sometimes list what was edited at the bottom of the post. If this ends up being longer than 2 lines, don't bother.
*'''We require all posts to be positive, constructive, and on topic'''. We reserve the right to remove any topics we deem inappropriate or disruptive to the LabVIEW community. Please note that, from time to time, topics may be removed for being inappropriate even though your individual post in that topic may have been perfectly fine. Please do not feel this reflects badly on you.
*'''No Spam'''. Spamming is not permitted; please keep all your posts as constructive and on-topic as possible. If you think a specific post is clearly spam use the report post to moderator button. Replying to such posts only adds visibility to them and makes the problem worse.

== Homework hustlers ==

Homework hustlers are those forum visitors that ask questions on the forums trying to get an easy solution to a school assignment. They do not try to put any effort on their own to solve the school assignment and want other forum members to give them the answer or solution to their problem. Homework Hustlers are not allowed on the Forums. No exceptions.

If you think a certain post is a homework hustling type question. Click on the report post to moderator button. This is the only recourse available to you. DO NOT respond to the post. You are not a moderator and posting negative or disrespectful comments will be considered abuse and results in a penalty by suspension of your account for a period of 2 days (see [[#Penalties for guideline and golden rule violations]]). If a post has been determined to be a Homework question, the guilty party will be contacted via PM and a clarification will be requested. If the issue is still not resolved to the satisfaction of a moderator, then the users' account will be deleted and all their posts removed.

== Glossary of useful forum terms ==

#Admin - (shortened form of Administrator); The ultimate gods of the Forums. They make the final decision on who can be banned, and other life-threatening questions.
#Banned - This is when you are not allowed to make anymore posts. Your IP address, E-mail address, and user name will prevent you to make anymore posts. This is extreeeeemly rare, and is preceded by a warning.
#LabVIEW FAQ - Frequently asked questions. The best resource for common questions.
#Flame war - a deliberate exchange of insults between two parties. This usually involves a series of insulting, irrelevant posts in the same thread.
#Kill - To delete a post.
#LQTM - Laughs Quietly To Myself - similar to, but usually more honest than, LOL (see below).
#LOL - Laughs Out loud.
#RMB - Right menu Button (used in LabVIEW)
#AFAIK - As far as I know
#Nuke - To maliciously destroy a thread.
#Mod - shortened form of Moderator); A moderator who has been given the power to delete/edit other people's posts. They are there to ensure that discussions are relevant and interesting. Don't worry, they only use their powers very sparingly. The moderators were chosen by God himself. God, what with being all-knowing and stuff, chose enough moderators to handle the load. Please don't ask to be made a moderator. We have enough, and you will only be disappointed.
#OCG - Modern interpretation to OMG (see below).
#OMG - Oh My God or Oh My Gosh - an expression of exclaimation.
#Regular - Someone who lives on the Forums. Their diet usually consists of waffles, syrup and Mountain Dew. Renowned for their general friendliness, regulars are far from being extinct. But please, support their cause by donating generously to the Poor Boy Foundation
#Thread - A topic started by one member to which anyone can reply. Discussions should be about the original topic.
#PM - Private Message
#IMHO - In my humble opinion, used to express one's meaning

== File downloads in the forums==

An important thing to keep in mind. This is of course, a public space and it behooves you and the health of your computer to take care in clicking on any links/files of unknown origin that someone may post in a thread. Sad as it may seem, there are unsocialized bone nuts out there that get their jollies by causing mayhem. Due to the immediate nature of the forums, we can't insure that a damaging file won't find its way onto the site, though we'll make every effort to keep things safe by removing them ASAP. Please inform the Forum admin or any moderators you see wandering around if you spy something suspicious. Exercise caution and keep your common sense meter turned on and properly calibrated. We cannot be held responsible for the content posted by other Forum users. It may very well happen that something posted, be it text, images, files, or links to any of these thing may be offensive to you. The LAVA moderators will do the best they can to keep the Forums clean of offensive posts, but with such a large community, it is impossible to screen every post quickly and efficiently. Also keep in mind that we highly regard free speech, so the protection of that right will be utmost in deeming what is appropriate. If you have any specific complaint about something offensive you have seen, please feel free to contact a moderator or administrator. The best prevention is sound judgment.

Information about file downloads in the [http://forums.lavag.org/downloads.html Code Repository] can be found [http://forums.lavag.org/Code-Repository-Discussions-f62.html here]:

== The golden forum rules ==

#There will be no excessive use of profanity.
#Do not abuse the PM system
#There will be no racial, ethnic, gender based insults or any other personal discriminations.
#There will be no posts meant to offend or hurt any other member, in a manner which is offensive or inflammatory. Respect new members trying to learn LabVIEW.
#Spamming is not permitted; please keep all your posts as constructive and on-topic as possible.
#Pornography, warez, or any other illegal transactions may NOT be linked in any shape or form.
#All posts are property of the poster. This forum and all web sites owned in conjunction with this forum have the right to request alteration or deletion of any offensive post. Posts may be deleted for any reasons the forum administrators or moderators deem reasonable.
#Users may not argue a moderators decision publicly. Any and all complaints directed at a moderator must first address the moderator in question via PM. If the problem can not be resolved, then the moderator and user must send their positions to the forum admin. The forum admin will make or change any and/or all final decisions.
#Pictures may be posted as long as they are not explicit or offensive.
#Please keep foul language to a minimum, any excessive un-called for language will be removed and you will receive a final warning.
#Remember to post in the correct forum. Take your time to look at other topics and see where your topic should go. If your topic is placed in the wrong forum, it will be moved by a moderator.
#If a topic is recognized as being posted in the wrong forum, or if the post is a violation of our guidelines then please contact a moderator either via PM (personal message) or the report post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a member's topic (which has been posted in error and requires locking or moving to another forum) will be sent a PM warning and placed into moderation queue upon further actions.
#Having fun is good, we like fun. There are general forums for non-programming related topics. Please keep it positive and polite. We do not censor opinions or ideas on our forums but we do take action against posts and/or topics that could cause unrest in the community beyond a civil and polite disagreement.
#Any impersonation of a user, Admin or moderator, in any mode of communication, is strictly prohibited and will result in a banning.
#Linked and locked topics are pruned regularly to reduce page clutter. If you have a question about where your topic went, please PM (personal message) a Moderator or Administrator before starting a new topic asking where it went, or posting a duplicate of the original topic. We will be happy to provide you with a link to the new location, or a reason why it was locked and/or removed.
#Homework Hustlers are not allowed on the Forums. No exceptions.
#LabVIEW serial number or registration key requests are NOT allowed. No exceptions.

== Penalties for guideline and golden rule violations ==

*Anyone found breaking the above rules and guidelines will have their account suspended for two (2) days.
*Anyone abusing the PM system will have their account suspended for four (4) days.
*If you repeatedly break the rules, your account will be permanently deleted and a ban placed on your registration info to prevent the account from being reused in the future.

All moderator decisions and outcomes (suspensions, deletions etc) will be kept private and confidential. This will allow offenders to recover from what may possibly be a mistake or error on their part or on the part of the moderators.

== Note ==
Only the moderators are authorized by the LAVA Forums to perform any user account suspension/deletion, post editing, post deletion and post moving. In addition, only moderators can decide if a post is a Homework question. Moderators do not read every post. This is impossible. Please use the '''report post to moderator''' button to bring anything to the attention of a moderator.
----

Remember, being a nice netizen will lead to respect, which leads to prompt answers and much fun. Do your best to be cordial, and you will see what a great thing the LabVIEW community is. If you have any questions about any issue brought up by this thread, feel free to ask the moderators, or your fellow Forumites.
Above all, have a nice day

== See also ==
*[http://forums.lavag.org/Tutorials-f72.html Tutorials on Using the Forums]
*[http://forums.lavag.org/Site-Feedback-and-Support-f27.html General Forums Feedback & Support]
*[http://forums.lavag.org/Suggestions-and-Ideas-f67.html Post Suggestions and Ideas for the Forums]
*[http://forums.lavag.org/Bug-Reports-f66.html Report a Forum Bug]

== External links ==
*[http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions the Smart Way]

[[category:LAVA]]

LabVIEW configuration file/Block Diagram

2008-08-27T22:38:53Z

Crelf:

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
}}
{{ 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 = viTitleInPalettes
| example = viTitleInPalettes=TRUE
| datatype = b
| description = Use Window Titles in function palettes
| 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
}}

[[Category:Development Environment|{{PAGENAME}}]]

LabVIEW configuration file/Block Diagram

2008-08-27T22:37:23Z

Crelf:

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
}}
{{ 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.0
| LV2 = 8.20
| LV3 = 8.5
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes = LabVIEW 8.5 only. 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 = viTitleInPalettes
| example = viTitleInPalettes=TRUE
| datatype = b
| description = Use Window Titles in function palettes
| 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
}}

[[Category:Development Environment|{{PAGENAME}}]]

Benchmarking Code Speed

2008-04-29T22:28:12Z

Crelf: New page: {{TOCnestright}} Benchmarking code speed can be difficult, mostly because it's often difficult to remove the testing environment from the unit to be tested. Here are some tips on creating...

{{TOCnestright}}
Benchmarking code speed can be difficult, mostly because it's often difficult to remove the testing environment from the unit to be tested. Here are some tips on creating a valid testing environment when testing code unit speed.

==Title A==
Text A.

==Title B==
Text B.

[[Category:Benchmarking|Code_Speed]]

Info-LabVIEW

2008-02-15T19:36:02Z

Crelf:

{{stub}}
Info-LabVIEW is an independent mailing list to discuss LabVIEW. Tom Coradeschi, originally formed the list when LabVIEW ran on Macintosh computers only (National Instruments released LabVIEW for Windows in 1992). The list has been running now for over 16 years and has become a LabVIEW institution. Today, Info LabVIEW keeps thousands[''citation needed''] of subscribers talking to each other. Although the vast majority of LabVIEW programmers use Windows[''citation needed''], Mac-specific questions still appear regularly.

==Milestone Posts==
* [http://sthmac.magnet.fsu.edu/infolabview/ILVDigests/1991/02/14/Info-LabVIEW_Digest_1991-02-14_001.html First Message] (1991-02-14)
* [http://sthmac.magnet.fsu.edu/infolabview/ILVDigests/1994/05/11/Info-LabVIEW_Digest_1994-05-11_007.html Gary Johnson's story of writing LabVIEW Graphical Programming] (1994-05-11)
* [http://sthmac.magnet.fsu.edu/infolabview/ILVDigests/1999/05/27/Info-LabVIEW_Digest_1999-05-27_025.html Greg McKaskle's "Rusty Nails" post] (1999-05-27)
* [http://sthmac.magnet.fsu.edu/infolabview/ILVDigests/2006/08/14/Info-LabVIEW_Digest_2006-08-14_006.html Jim Kring's announcement that LabVIEW for Everyone, 3rd edition ships] (2006-08-14)

== See also ==
*[[Info-LabVIEW mailing list archive]]

== External links ==
*[http://sthmac.magnet.fsu.edu/infolabview/subscribe.html Subscribe to Info-LabVIEW]
*[http://sthmac.magnet.fsu.edu/infolabview/ Info-LabVIEW home]

[[Category:Communities]]

LabVIEW configuration file/Front Panel

2007-11-07T18:19:46Z

Crelf:

This is a list of LabVIEW ini File settings relating to Front Panel behaviour.

{{ labviewconfigurationkey
| keyname = blinkFG
| example =blinkFG=00EF12FF
| datatype =i
| description =Color of foreground blink of FP components (xxRRGGBB)
| permitted_values =0x00 to 0x00FFFFFF
| default =Unknown
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}
{{ labviewconfigurationkey
| keyname = blinkBG
| example =blinkFG=001100FF
| datatype =i
| description =Color of background blink of FP components (xxRRGGBB)
| permitted_values =0x00 to 0x00FFFFFF
| default =Unknown
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}
{{ labviewconfigurationkey
| keyname = blinkSpeed
| example =blinkSpeed=250
| datatype =i
| description =Blink speed (milliseconds)
| permitted_values =1 to 232
| default =1000
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}
{{ labviewconfigurationkey
| keyname = doubleClickToEditControl
| example =doubleClickToEditControl=TRUE
| datatype =b
| description =Open the control editor with double click
| 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 = noBoxAroundName
| example =noBoxAroundName=FALSE
| datatype =b
| description =Use transparent name labels
| 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 = offscreenUpdates
| example =offscreenUpdates=FALSE
| datatype =b
| description =Use smooth updates during drawing
| 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 = returnKeyAction
| example =returnKeyAction=TRUE
| datatype =b
| description =End text entry with Return key
| 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 = sunKeyboard
| example =sunKeyboard=TRUE
| datatype =b
| description =Support numeric keypad
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =u
| OS2 =
| OS3 =
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = useAllFKeys
| example =useAllFKeys=FALSE
| datatype =b
| description =Override system default function key settings
| 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 = useLocaleDecimalPt
| example =useLocaleDecimalPt=FALSE
| datatype =b
| description =Use localized decimal point
| 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
}}

[[Category:Development Environment]]

Aspects of error handling

2007-10-30T02:09:42Z

Crelf: Added basic error info.

{{Template:ActiveDiscuss}}
Writing VIs and SubVIs that incorporate error handling is considered good form, not only to allow the user indication of abnormal software execution, but also to allow the software to make decisions based on the status of previous operations. Including error clusters in your code assists in troubleshooting, modularity, and user friendliness.

== The Error Cluster ==
The error cluster is a predefined LabVIEW cluster that is used to contain error status information. The cluster contains the following three components:

{| class="wikitable"
|-
! Name
! Data Type
! Description
|-
| Status
| Boolean
| Indicates if an error has occurred (TRUE = error, FALSE = no error).
|-
| Code
| 32-Bit signed integer
| A standardized error code specific to the particular error. LabVIEW has a table of default error codes, although the user is able to define custom error codes. See below for more information.
|-
| Source
| String
| Textual information often describing the error and the VI it occurred within.
|}

== Usage ==
Although one of the most obvious methods of conditional code execution might be to unbundle the Status Boolean of the error cluster, and feed it to the conditional terminal of a case structure (figure coming soon...), the complete cluster can be wired to it instead (figure coming soon...). The functionality of the code in (figure coming soon...) and (figure coming soon...) is identical, although its readability is vastly improved as the second example colors the case structure green for the No Error case, and red for the Error case. Wrapping the entire code of a SubVI within a conditional case structure based on the error input allows VIs at higher levels to continue functioning, without executing code that could be useless or even dangerous when an error has occurred. Consider the simple report generation example shown in (figure coming soon...).

A report is initially created, a file is then attached, the report is printed, and finally destroyed. The dataflow link between these SubVIs is the report’s reference number (refnum), which ensures each execute in a predefined order. If each of the SubVIs execute without error, then the process completes successfully. Conversely, if one of the SubVIs encounters an error, subsequent SubVIs are unaware of the problem and attempt to execute regardless. In the example above, an error in the Attach a File to the Report SubVI will not cause the Print the Report SubVI to fail, resulting in a blank report print. If effective error handling is introduced (figure coming soon...), the Print the Report SubVI will know if an error has occurred before its execution is requested. If the functional code inside the Print the Report SubVI is enclosed within a conditional case structure based on the error input, the printing code is bypassed, and the error cluster is passed on to the next SubVI.

To attain a higher level of user interaction, standard SubVIs exist to alert the user to an error on the error cluster, and prompt for conditional actions. The Simple Error Handler.vi (figure coming soon...) allows for a basic level of error cluster status reporting, displaying detected errors in a dialog box, and prompting the user for an action based on the type of dialog input (for example, OK, Cancel, Stop, etc.).

The Simple Error Handler.vi is a wrapper for the lower level General Error Handler.vi. The latter (figure coming soon...) is more configurable, and permits the dynamic definition of custom error codes, and error exception handling. LabVIEW 7.0 brings with it an addition to the error handling function palette, Clear Errors.vi (figure coming soon...). This VI is simply an error in control and an
error out indicator, which are not linked on the wiring diagram, causing any errors on the wired error link to be cancelled. This VI can be useful when constructing custom error-handling VIs, including dialog boxes allowing user interaction that is not covered by the simple and general error-handling VIs, but should not be used alone. Although dumping the errors from the error cluster may be tempting, one must incorporate appropriate code to handle them.

== Wiring Errors into a SubVI Connector Pane ==
As described above, SubVIs have an associated connector pane, and the placement of error cluster inputs and output is generally in the lower quadrants (error in on the left, and error out on the right), with corresponding exclamation marks over the connectors on the SubVI’s icon (figure coming soon...).

== Default Error Codes ==
The LabVIEW execution system contains a large list of standard and specific errors, encouraging the reuse of generic codes across applications. A list of generic errors codes can be found under the LabVIEW Help menu (figure coming soon...). Another method of parsing a small number of errors is to select the Help Explain Error menu item. This will launch an interface that allows the user to enter an error code, and a brief explanation is displayed (figure coming soon...). This interface is also accessible by right-clicking on a front panel error cluster, and selecting Explain Error.

== Custom Error Codes ==
National Instruments has set several error codes aside for custom use. If an existing error code does not adequately describe the error condition, the user can define custom codes that are specific to the application. Codes between 5000 through to 9999 are available for use, and do not need to conform to any other application. Although General Error Handler.vi can be used to define custom error codes, one can also create an XML file in the labview\user.lib\errors directory that contains custom error codes and their descriptions. This method is particularly useful if the user requires custom error codes to apply to several applications, or if the codes are used by several software engineers in a team or are to be distributed with an application.

For example, the XML filename must be in the format '''*-errors.txt''' (where '''*''' is user definable), and the internal file structure must adhere to the following format:

<blockquote> 
<?XML Version="1.0"> 
<nidocument> 
<nicomment> 
This is a custom error code definition file for my application. 
</nicomment> 
<nierror code="5000"> 
User Access Denied! 
Contact the Security Department to gain clearance to perform this function. 
</nierror> 
<nierror code="5001"> 
User Unknown. 
Contact the People Development Department. 
</nierror> 
<nierror code="5100"> 
Driver Unable to Contact Instrument Database. 
Contact the Software Engineering Department Helpdesk. 
</nierror> 
<nierror code="5200"> 
Plug-In Module in R&D mode – not to be used in Production Environment. 
Contact the New Product Development Group. 
</nierror> 
</nidocument>
</blockquote>

As can be seen, a file comment can be created within the <nicomment> tag space. Each custom error is defined as an <nierror> with it’s associated error code, and its error message is then placed inside the <nierror> tag space. Although hand coding a custom error code XML file is possible, the Error Code File Editor (Tools->Advanced->Edit Error Codes) provides a simple GUI for file creation and editing (figure coming soon...). Once custom error code files have been created and/or altered, LabVIEW must be
restarted for the changes to take effect. It is often useful to define code bands during the project planning stage, setting aside bands for specific related error groups.

----
'''Note''':
This entire section of WIKI about "Error Handling" could benefit from a deep reading of the online help for the General Error Handler.vi. That VI has more facilities than folks typically know. FOR EXAMPLE:

The General Error Handler.vi includes an input parameter for the type of dialog, one option is "no dialog." I would STRONGLY recommended instead of calling "Error Code Database.vi". The primary reason for the recommendation is that the translation of error code cluster into human readable strings involves much more than just looking up text in the database. The '''source''' string itself may include information to override or extend the database, and the text in either the '''source''' string or the database may include formatting commands, such as HTML tags for bold face. Encoding information in the '''source''' string is a technique that will become more common in the future.

You may desire to display the text, fully formatted, in a string indicator of your own instead of in any dialog. Use the function of General Error Handler CORE.vi (found on the block diagram of General Error Handler.vi) to do this.

[[category:LabVIEW fundamentals]]

Color

2007-10-29T23:28:56Z

Crelf:

'''Colors''' are represented in LabVIEW by an unsigned 32-bit integer. The integer is of the hexadecimal form 0x00RRGGBB, where RR, GG, and BB represent the red, green, and blue components of the color, respectively.

[[category:data types]]
{{stub}}

Functional global variable

2007-06-07T14:42:29Z

Crelf: /* Alternative Nomenclature */

Functional Globals are VIs that allow controlled access to data or resources, often allowing various actions to be performed. Functional Globals (FGs) most often make use of uninitialized shift registers (USRs). USRs are shift registers that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.

==Alternative Nomenclature==
Functional Globals are known by various names among LabVIEW programmers.
*LV2 globals – because LV2 supported uninitialized shift registers
*USR globals – since most FGs make use of uninitialized shift registers
* VIG - "VI Global" as the VI performs the functionality of a global
*Action Engines – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

==Structure==
The most common form of a Functional Global is a [[While Loop]] with a TRUE wired to the stop condition. This forces the loop to terminate after just one execution, meaning the while loop is only used to provide a place to put USRs. A [[For Loop]] could also be used with a constant wired to the count terminal. Another method is to use a single-element queue to store the data, though this requires more mouse clicks to implement. The performance of each of these is very close and most likely will vary a little from computer to computer.

[[Image:Simple_FG.PNG|frame|center|Simple Functional Global using a While Loop]]

In order to specify what action to perform, an [[enumerated type]] is often used as an input to the Functional Global. Other methods are possible (Booleans, First Call?, etc.), but an enumerated type provides for a readable, extensible list of actions. Furthermore, saving the enumerated type as a typedef control makes any changes to the list automatically update wherever the Functional Global is used in the code. The ‘action’ input is fed to a case structure which contains the code to implement for each of the defined actions.

For more complex situations, multiple actions can be performed on a single call to the FG. This can be a straightforward [[state machine]], or it can allow for different actions based on the data received or on the existence of resources, etc.

The data in a Functional Global could be of any type, but very often there will be several data elements in a single FG. It is helpful to group the data into a cluster to limit the number of wires entering and leaving the FG. Designing the data structures and how you cluster your data should be done early on, rather than haphazardly growing your clusters as you grow your program.

In order to deal with varying input requirements on the different actions, one can create ‘wrappers’ around the Functional Global that allow for different inputs to be required. This also gives the benefit of being able to search your code for certain actions as you can search for a specific VI, but not a specific enumerated type’s value.

==Uses==
The primary use of Functional Globals is to provide data sharing across an entire project, both horizontally and vertically. Horizontal sharing means multiple top-level VIs running autonomously can all have access to the same data. Vertical sharing means that subVIs at any depth will have access to the data without requiring explicit passing of parameters through VI [[connector pane]] terminals. These are common issues in even small-sized programs.

Another common use is to encapsulate some functionality, especially functionality that is linked to persistent data or resources like files or devices. This encapsulation protects the resource and provides an extensible interface for interacting with the data or resource. The encapsulation also allows you to avoid a plethora of shift registers in a single VI. You can offload the shift-register to the Functional Global, and call it when needed, without worrying about wiring the data through all your case structures.

To get a better idea of what can be done with Functional Globals, here is a list of things that can be done:
*Load information from a file into a FG, access it anywhere in your program
*Maintain your system’s configuration parameters in one location.
*Store a control reference (like a tree control) in a FG, and then define an interface to manage that control. For complex controls like trees and multi-column listboxes this can simplify your top-level code.
*Timers are well implemented with FGs. You can keep the start time in the shift register, and then check the elapsed time when you call it again.
*Automatically preallocate an array when the FG is first called, then use “Replace Array Subset” to efficiently manipulate the array.
*Keep an ‘Undo’ list (stack) that allows you to push changes onto a stack, and pop them off when you need to undo the change.
The list could go on and on – whatever you can dream up!

==Race Conditions and Locking==
One of the main reasons that Functional Globals are encouraged in lieu of [[global variable]]s is race conditions. The majority of Functional Globals are, by definition, not reentrant so that different calls to the FG will all refer to the same shift registers and hence the same data or resource. This means that when a VI calls a FG, that FG is locked or reserved for use by the calling VI. Other VIs need to wait until it is done before they can call the FG.

Global variables are reentrant. If you try to write a value to the global in several places in your code, updates to the value are unpredictable with respect to time. This means that changes to the global can be subject to race conditions. This is especially true if you read/write to the global where a race condition could occur between the read and the write of the variable.

The downside for Functional Globals is that the locking that takes place can be a bottleneck in the code if many VIs are trying to access the FG at the same time. The majority of applications will not have a problem, but care must be taken if speed is a concern.

It is also important to note that Functional Globals are not a cure-all for race conditions. If actions on the Functional Global are not atomic (i.e. they require more than one call to the FG) then race conditions are still possible. Race conditions are only eliminated if all updates to the data are done inside the FG, in a single call. Here are a couple ways to still allow race conditions with FGs.
*Ask for the data from the FG, change it, and then write it back to the FG.
*Successive modifications, such as {Set data, normalize data, sort data, output max} By the time you sort the data, new data could have been set that hasn’t been normalized.

==Benefits==
#Efficient Memory Usage – Because the VI retains the same data space regardless of it use in the code, only a single call to the memory manager is made. If arrays are stored in the USR, and replace array element primitives used, then the memory space is efficiently used wherever the VI is called.
#Reduces problems with race conditions, as discussed above.
#Error checking can be done on data writes (Global variables don’t allow this).
#High-level code more readable – By moving shift registers and code logic into Functional Globals with readable action lists, top-level code become simpler and cleaner.
#Reuse. Many FGs are generic enough to be used over and over again.

==Concerns==
===Busy connector panes===
Terminals get used up quickly, so be sure to design well up front and choose a connector pane with more terminals than you need. You can avoid excessive terminal usage by grouping all of your data into a cluster (preferably, a [[Type Definition]]) that is passed in and out of your functional global which will allow you to bundle and unbundle specific variables as needed on your main VI.

===Data Persistence===
Data in a USR, and hence in a Functional Global, disappears if the owning VI goes out of memory. When a VI runs for the first time, all of its subVIs that are not already in memory are loaded into memory and they belong to that parent VI. If that parent VI is stopped, all of the subVIs that belong to it are also released from memory – even if there are other VIs in memory still referencing those subVIs. The next time one of those subVIs is run, it is loaded into memory again and that calling VI becomes the new parent VI. But if there was anything stored in USRs, that data is now gone.

This behavior is different from a queue reference, for instance, where the queue is only destroyed when ALL VIs referencing it leave memory. It means that if you use Functional Globals across multiple top-level VIs, then you need to have a VI that is run first and contains all of your Functional Globals as subVIs. This ‘First Run’ VI must stay in memory until all other top-level VIs are closed to insure that the Functional Global data will be available.

==Reentrant functional globals==
===Unshared data===
There are certain problems where you do not need to share the persistent data elsewhere in the code. If you create a '''windowed average''' VI, it can be made reentrant and can be used in multiple places in your code to average data streams. This is an example of an in-place operation that is not shared, but requires persistent data. Timing a process in a single loop could be done with one instance of a Functional Global. Making this timing FG reentrant allows the developer to use that same timing FG to time other processes. See [[Reentrant VI]] for more information.

===By reference===
It’s possible to make use of reentrancy to duplicate functional globals. This allows to create as many globals as you need (even at run time) without duplicating code or modifying the original FG. The main disadvantage of this technique is the necessity to keep a reference to every instance of the functional global and pass them to the VIs or subVIs that will use them.

With this method, the only change to the original FG is to make the VI reentrant. Keep in mind that, from now on, this functional global can’t be used in the habitual way, since any instance will retain its own values.

To create an instance of the functional global, open it with the '''Open VI Reference''' function (use option 0x08 to prepare for reentrant run) and use the output reference to set the control values, run the VI and get the results. To facilitate things an avoid mistakes when getting/setting values, may be advisable to use the '''Call by Reference node'''. Furthermore, the encapsulation of the FG actions in specific wrappers, as detailed in the Structure section above, is also useful.

==See Also==
*[[Global variable]]
*[[State machine]]

==External Links==
*[http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328 NI Forums Community Nugget on Action Engines]
*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]

LabVIEW configuration file/Easter Eggs

2007-05-07T23:16:57Z

Crelf:

{{LabVIEW configuration back}}
This is a list of LabVIEW ini File settings relating to Easter Eggs - the messages that NI R&D have hidden in there. Essentially, they have no functional advantage, but are a bit-o-fun.

== HiliteExecutionPride ==
Example: <code>HiliteExecutionPride=TRUE</code> 
Description: Changes the highlight execution bubbles that traverse the wires from a circle into a small NI logo 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: None 

== ICantBelieveItsNotButter ==
Example: <code>ICantBelieveItsNotButter=TRUE</code> 
Description: Changes the LabVIEW splash screen to a most delcious shade of yellow 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 6.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: None 

== ILuvLV20 ==
Example: <code>ILuvLV20=TRUE</code> 
Description: Adds an impressive birthday cake ot the "About" screen 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 8.20 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: None 

== TwentyYears ==
Example: <code>TwentyYears=TRUE</code> 
Description: Adds the following text to the splash screen on launch: "Thank you for 20 years of Dataflow..." 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 8.20 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: None

LabVIEW configuration file/Easter Eggs

2007-05-07T22:43:10Z

Crelf:

LabVIEW configuration file/Easter Eggs

2007-05-07T22:14:32Z

Crelf: New page: {{LabVIEW configuration back}} This is a list of LabVIEW ini File settings relating to Easter Eggs - the messages that NI R&D have hidden in there. Essentially, they have no functional ad...

LabVIEW configuration file

2007-05-07T22:09:59Z

Crelf: /* Settings Descriptions */

This article contains information related to the LabVIEW configuration file. This file is used by LabVIEW to store configuration information related to the LabVIEW development environment. If you are interested in finding out how to read and write your own [[configuration file]] then see the article on the [[configuration file|configuration file VIs]].
== Editing the .\labview.ini File - A Disclaimer ==

The options that aren't in the preferences dialog are generally considered to be not useful or even harmful. They are sometimes there to allow National Instruments a backdoor or a workaround for when the LabVIEW development team changes a behavior. They are also used to turn on obscure development features that the developers use to make or debug LabVIEW. These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful. 
The LabVIEW developers have never tried to hide any of these strings, but it is unlikely that you will gain any benefit from trying out various combinations of the settings. If you ask technical support what a setting is, they will likely tell you that they have no idea. They are telling you the truth. 
Even some of the folks in NI R&D may not know what some of the settings do without checking the code. Others, such as exoticcontrols, no longer do anything. It was once used to show a control palette submenu that contained controls that were still in work and not ready for prime-time. They were experiments, unsupported features, and guaranteed to crash if you did much with them. Just the sort of thing that is needed for development, but not useful to even advanced LabVIEW users unless they have a death-wish. 
If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LabVIEW left it. Don't ask tech support to fix it or complain that the LabVIEW attic has rusty nails and splinters. 
Resedit is a low level tool that in the right hands is useful, in the wrong hands, well, its in the wrong hands. For the person that likes taking a multimeter and a soldering iron to computers and household appliances, its exactly what you always wanted. If you start monkeying with things in the resources or the .ini file, use common sense and do it on a copy or you will just end up reinstalling LabVIEW. 
Once the fun and experimentation is over with, I think you will agree that the useful options, with very few exceptions are in the Preferences dialog. 

== Settings Descriptions ==
This is a relatively comprehensive list of the settings that can be included in a .\labview.ini file (or a compiled executable's ini file). Whilst some of these settings appera in the files by default, others may only appear when the features used require them to be there, whilst others still can only be added manually to provide access to backdoor settings and operations.

LabVIEW ini Settings are organised into the following categories (in alphabetical order):
# [[LabVIEW_ini_File.Block_Diagram|Block Diagram]]
# [[LabVIEW_ini_File.Colors|Colors]]
# [[LabVIEW_ini_File.Debugging|Debugging]]
# [[LabVIEW_ini_File.Execution_System|Execution System]]
# [[LabVIEW_ini_File.Fonts|Fonts]]
# [[LabVIEW_ini_File.Front_Panel|Front Panel]]
# [[LabVIEW_ini_File.History|History]]
# [[LabVIEW_ini_File.Miscellaneous|Miscellaneous]]
# [[LabVIEW_ini_File.Paths|Paths]]
# [[LabVIEW_ini_File.Performance|Performance]]
# [[LabVIEW_ini_File.Printing|Printing]]
# [[LabVIEW_ini_File.Time_and_Date|Time and Date]]
# [[LabVIEW_ini_File.VI_Server|VI Server]]
# [[LabVIEW_ini_File.Web_Server|Web Server]]
# [[LabVIEW_ini_File.Unknown|Unknown]] - do you recognise any of these?
# [[LabVIEW_ini_File.Easter_Eggs|Easter Eggs]] - reveal hidden messages (no functional advantage, but a bit-o-fun)

* Add your own ini setting descriptions using these [[LabVIEW_ini_File.Key_Templates|wiki templates]]

----

== See Also ==
[[Custom LabVIEW configuration file]]
== External Links ==
* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/customizing_your_work_environment/#How_LabVIEW_Stores_Options NI.com online help for LV configuration files]
* [http://sthmac.magnet.fsu.edu/labview/LVOptionsList.html Scott Hannahs's LabVIEW Info Page]

[[Category:Development Environment]]

LabVIEW configuration file/Paths

2007-05-07T22:00:12Z

Crelf: /* defaultdir */

{{LabVIEW configuration back}}
This is a list of LabVIEW ini File settings relating to Paths.

== defaultdir ==
Example: <code>defaultdir="C:\Program Files\National Instruments\LabVIEW 8.2\"</code> 
Description: Default Directory 
Datatype: Path 
Permitted Values: Any existing disk path 
Default Value: [[Image:logo.Windows.png]][[Image:logo.Mac.png]] The installed LabVIEW folder, [[Image:logo.Linux.png]][[Image:logo.Sun.png]] The user home folder 
LabVIEW Versions: 5.x, 6.x, 7.1, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: None 

== libdir ==
Example: <code>libdir="C:\Program Files\National Instruments\LabVIEW 8.2\"</code> 
Description: Library Directory 
Datatype: Path 
Permitted Values: Any existing disk path 
Default Value: <code>..\LabVIEW x.x\</code> 
LabVIEW Versions: 5.x, 6.x, 7.1, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: None. 

== menusdir ==
Example: <code>menusdir="C:\Program Files\National Instruments\LabVIEW 8.2\menus"</code> 
Description: Menus Directory 
Datatype: Path 
Permitted Values: Any existing disk path 
Default Value: <code>..\LabVIEW x.x\menus\</code> 
LabVIEW Versions: 5.x, 6.x, 7.1, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: None. 

== tmpdir ==
Example: <code>tmpdir="C:\DOCUME~1\USERNA~1\LOCALS~1\Temp\"</code> 
Description: Temporary Directory 
Datatype: Path 
Permitted Values: Any existing disk path 
Default Value: The OS-reported temporary folder (as read from the <code>TMP</code> environment variable) 
LabVIEW Versions: 5.x, 6.x, 7.1, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: None. 

== viSearchPath ==
Example: <code>viSearchPath="<topvi>:\*;<foundvi>:\;<vilib>:\*;<userlib>:\*;<instrlib>:\*"</code> 
Description: VI Search Path 
Datatype: [Path] 
Permitted Values: Any existing disk paths 
Default Value: <code>"<topvi>:\*;<foundvi>:\;<vilib>:\*;<userlib>:\*;<instrlib>:\*"</code> 
LabVIEW Versions: 5.x, 6.x, 7.1, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: The locations that LabVIEW will search through to find components that aren't in their expected location

LabVIEW configuration file

2007-05-07T21:46:56Z

Crelf: /* Settings Descriptions */

This article contains information related to the LabVIEW configuration file. This file is used by LabVIEW to store configuration information related to the LabVIEW development environment. If you are interested in finding out how to read and write your own [[configuration file]] then see the article on the [[configuration file|configuration file VIs]].
== Editing the .\labview.ini File - A Disclaimer ==

The options that aren't in the preferences dialog are generally considered to be not useful or even harmful. They are sometimes there to allow National Instruments a backdoor or a workaround for when the LabVIEW development team changes a behavior. They are also used to turn on obscure development features that the developers use to make or debug LabVIEW. These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful. 
The LabVIEW developers have never tried to hide any of these strings, but it is unlikely that you will gain any benefit from trying out various combinations of the settings. If you ask technical support what a setting is, they will likely tell you that they have no idea. They are telling you the truth. 
Even some of the folks in NI R&D may not know what some of the settings do without checking the code. Others, such as exoticcontrols, no longer do anything. It was once used to show a control palette submenu that contained controls that were still in work and not ready for prime-time. They were experiments, unsupported features, and guaranteed to crash if you did much with them. Just the sort of thing that is needed for development, but not useful to even advanced LabVIEW users unless they have a death-wish. 
If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LabVIEW left it. Don't ask tech support to fix it or complain that the LabVIEW attic has rusty nails and splinters. 
Resedit is a low level tool that in the right hands is useful, in the wrong hands, well, its in the wrong hands. For the person that likes taking a multimeter and a soldering iron to computers and household appliances, its exactly what you always wanted. If you start monkeying with things in the resources or the .ini file, use common sense and do it on a copy or you will just end up reinstalling LabVIEW. 
Once the fun and experimentation is over with, I think you will agree that the useful options, with very few exceptions are in the Preferences dialog. 

== Settings Descriptions ==
This is a relatively comprehensive list of the settings that can be included in a .\labview.ini file (or a compiled executable's ini file). Whilst some of these settings appera in the files by default, others may only appear when the features used require them to be there, whilst others still can only be added manually to provide access to backdoor settings and operations.

LabVIEW ini Settings are organised into the following categories (in alphabetical order):
# [[LabVIEW_ini_File.Block_Diagram|Block Diagram]]
# [[LabVIEW_ini_File.Colors|Colors]]
# [[LabVIEW_ini_File.Debugging|Debugging]]
# [[LabVIEW_ini_File.Execution_System|Execution System]]
# [[LabVIEW_ini_File.Fonts|Fonts]]
# [[LabVIEW_ini_File.Front_Panel|Front Panel]]
# [[LabVIEW_ini_File.History|History]]
# [[LabVIEW_ini_File.Miscellaneous|Miscellaneous]]
# [[LabVIEW_ini_File.Paths|Paths]]
# [[LabVIEW_ini_File.Performance|Performance]]
# [[LabVIEW_ini_File.Printing|Printing]]
# [[LabVIEW_ini_File.Time_and_Date|Time and Date]]
# [[LabVIEW_ini_File.VI_Server|VI Server]]
# [[LabVIEW_ini_File.Web_Server|Web Server]]
# [[LabVIEW_ini_File.Unknown|Unknown]] - do you recognise any of these?

* Add your own ini setting descriptions using these [[LabVIEW_ini_File.Key_Templates|wiki templates]]

----

== See Also ==
[[Custom LabVIEW configuration file]]
== External Links ==
* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/customizing_your_work_environment/#How_LabVIEW_Stores_Options NI.com online help for LV configuration files]
* [http://sthmac.magnet.fsu.edu/labview/LVOptionsList.html Scott Hannahs's LabVIEW Info Page]

[[Category:Development Environment]]

LabVIEW configuration file

2007-05-07T21:46:43Z

Crelf: /* Settings Descriptions */

This article contains information related to the LabVIEW configuration file. This file is used by LabVIEW to store configuration information related to the LabVIEW development environment. If you are interested in finding out how to read and write your own [[configuration file]] then see the article on the [[configuration file|configuration file VIs]].
== Editing the .\labview.ini File - A Disclaimer ==

The options that aren't in the preferences dialog are generally considered to be not useful or even harmful. They are sometimes there to allow National Instruments a backdoor or a workaround for when the LabVIEW development team changes a behavior. They are also used to turn on obscure development features that the developers use to make or debug LabVIEW. These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful. 
The LabVIEW developers have never tried to hide any of these strings, but it is unlikely that you will gain any benefit from trying out various combinations of the settings. If you ask technical support what a setting is, they will likely tell you that they have no idea. They are telling you the truth. 
Even some of the folks in NI R&D may not know what some of the settings do without checking the code. Others, such as exoticcontrols, no longer do anything. It was once used to show a control palette submenu that contained controls that were still in work and not ready for prime-time. They were experiments, unsupported features, and guaranteed to crash if you did much with them. Just the sort of thing that is needed for development, but not useful to even advanced LabVIEW users unless they have a death-wish. 
If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LabVIEW left it. Don't ask tech support to fix it or complain that the LabVIEW attic has rusty nails and splinters. 
Resedit is a low level tool that in the right hands is useful, in the wrong hands, well, its in the wrong hands. For the person that likes taking a multimeter and a soldering iron to computers and household appliances, its exactly what you always wanted. If you start monkeying with things in the resources or the .ini file, use common sense and do it on a copy or you will just end up reinstalling LabVIEW. 
Once the fun and experimentation is over with, I think you will agree that the useful options, with very few exceptions are in the Preferences dialog. 

== Settings Descriptions ==
This is a relatively comprehensive list of the settings that can be included in a .\labview.ini file (or a compiled executable's ini file). Whilst some of these settings appera in the files by default, others may only appear when the features used require them to be there, whilst others still can only be added manually to provide access to backdoor settings and operations.

LabVIEW ini Settings are organised into the following categories (in alphabetical order):
# [[LabVIEW_ini_File.Block_Diagram|Block Diagram]]
# [[LabVIEW_ini_File.Colors|Colors]]
# [[LabVIEW_ini_File.Debugging|Debugging]]
# [[LabVIEW_ini_File.Execution_System|Execution System]]
# [[LabVIEW_ini_File.Fonts|Fonts]]
# [[LabVIEW_ini_File.Front_Panel|Front Panel]]
# [[LabVIEW_ini_File.History|History]]
# [[LabVIEW_ini_File.Miscellaneous|Miscellaneous]]
# [[LabVIEW_ini_File.Paths|Paths]]
# [[LabVIEW_ini_File.Performance|Performance]]
# [[LabVIEW_ini_File.Printing|Printing]]
# [[LabVIEW_ini_File.Time_and_Date|Time and Date]]
# [[LabVIEW_ini_File.VI_Server|VI Server]]
# [[LabVIEW_ini_File.Web_Server|Web Server]]
# [[LabVIEW_ini_File.Unknown|Unknown]] - do you recognise any of these?

* Add your own ini setting descriptions using these [[LabVIEW_ini_File.Key_Templates|wiki templates]]

----

== See Also ==
[[Custom LabVIEW configuration file]]
== External Links ==
* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/customizing_your_work_environment/#How_LabVIEW_Stores_Options NI.com online help for LV configuration files]
* [http://sthmac.magnet.fsu.edu/labview/LVOptionsList.html Scott Hannahs's LabVIEW Info Page]

[[Category:Development Environment]]

LabVIEW configuration file

2007-05-07T21:46:32Z

Crelf: /* Settings Descriptions */

This article contains information related to the LabVIEW configuration file. This file is used by LabVIEW to store configuration information related to the LabVIEW development environment. If you are interested in finding out how to read and write your own [[configuration file]] then see the article on the [[configuration file|configuration file VIs]].
== Editing the .\labview.ini File - A Disclaimer ==

The options that aren't in the preferences dialog are generally considered to be not useful or even harmful. They are sometimes there to allow National Instruments a backdoor or a workaround for when the LabVIEW development team changes a behavior. They are also used to turn on obscure development features that the developers use to make or debug LabVIEW. These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful. 
The LabVIEW developers have never tried to hide any of these strings, but it is unlikely that you will gain any benefit from trying out various combinations of the settings. If you ask technical support what a setting is, they will likely tell you that they have no idea. They are telling you the truth. 
Even some of the folks in NI R&D may not know what some of the settings do without checking the code. Others, such as exoticcontrols, no longer do anything. It was once used to show a control palette submenu that contained controls that were still in work and not ready for prime-time. They were experiments, unsupported features, and guaranteed to crash if you did much with them. Just the sort of thing that is needed for development, but not useful to even advanced LabVIEW users unless they have a death-wish. 
If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LabVIEW left it. Don't ask tech support to fix it or complain that the LabVIEW attic has rusty nails and splinters. 
Resedit is a low level tool that in the right hands is useful, in the wrong hands, well, its in the wrong hands. For the person that likes taking a multimeter and a soldering iron to computers and household appliances, its exactly what you always wanted. If you start monkeying with things in the resources or the .ini file, use common sense and do it on a copy or you will just end up reinstalling LabVIEW. 
Once the fun and experimentation is over with, I think you will agree that the useful options, with very few exceptions are in the Preferences dialog. 

== Settings Descriptions ==
This is a relatively comprehensive list of the settings that can be included in a .\labview.ini file (or a compiled executable's ini file). Whilst some of these settings appera in the files by default, others may only appear when the features used require them to be there, whilst others still can only be added manually to provide access to backdoor settings and operations.

LabVIEW ini Settings are organised into the following categories (in alphabetical order):
# [[LabVIEW_ini_File.Block_Diagram|Block Diagram]]
# [[LabVIEW_ini_File.Colors|Colors]]
# [[LabVIEW_ini_File.Debugging|Debugging]]
# [[LabVIEW_ini_File.Execution_System|Execution System]]
# [[LabVIEW_ini_File.Fonts|Fonts]]
# [[LabVIEW_ini_File.Front_Panel|Front Panel]]
# [[LabVIEW_ini_File.History|History]]
# [[LabVIEW_ini_File.Miscellaneous|Miscellaneous]]
# [[LabVIEW_ini_File.Paths|Paths]]
# [[LabVIEW_ini_File.Performance|Performance]]
# [[LabVIEW_ini_File.Printing|Printing]]
# [[LabVIEW_ini_File.Time_and_Date|Time and Date]]
# [[LabVIEW_ini_File.VI_Server|VI Server]]
# [[LabVIEW_ini_File.Web_Server|Web Server]]
# [[LabVIEW_ini_File.Unknown|Unknown]] - do you recognise any of these?
 
* Add your own ini setting descriptions using these [[LabVIEW_ini_File.Key_Templates|wiki templates]]

----

== See Also ==
[[Custom LabVIEW configuration file]]
== External Links ==
* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/customizing_your_work_environment/#How_LabVIEW_Stores_Options NI.com online help for LV configuration files]
* [http://sthmac.magnet.fsu.edu/labview/LVOptionsList.html Scott Hannahs's LabVIEW Info Page]

[[Category:Development Environment]]