LabVIEW Wiki - User contributions [en]

EXE has the wrong date

2009-01-29T22:38:23Z

Jpdrolet:

Under some operating systems a built application in LabVIEW versions 5 and 6 (specifically Windows based machines) has the last modified date reported by Windows for the application exe file consistently set to the same value and not to the current date and time? This occurs regardless of the settings of the system clock. It appears that this is a bug in the Windows operating system. As far as we are aware, Microsoft has been aware of it for at least three years but the bug does exist at least under Windows 95 and 98. It is unknown whether the newer versions of Windows (including NT) still exhibit this problem.

The problem occurs when the LabVIEW Appliction Builder copies the standalone stub from the APPLIBS directory (applib.llb) to the exe file and appends the VI code to it. The Windows functions used for this should modify the modified date of the file but leave it at the date of the original stub file. Although NI could theoretically add a manipulation to the Application Builder which really "touches" the file to update the modification date, this is only a workaround for someone elses bug.

There are a couple of user workarounds. If you are not parcelling up your application into distribution disks you can "touch" the built exe with the linux utility of the same name (free downloads of win32 based touch utilities are available on the net; e.g. from the CygWin project.

[http://sources.redhat.com/cygwin/ http://sources.redhat.com/cygwin/]

Alternatively you could write a small application that reads one byte of the file and then writes that byte back to the file, thereby updating the modification time and date.You could also modify the applib.llb stub file directly just before building the application with either of the touch methods described above. This modification of the stub file will at least ensure that the files heading for the distribution disks end up with a file time and date close to that of the final build process.

[[category:building executables]]

Refnum descriptor

2008-03-17T23:36:14Z

Jpdrolet: addition of 0x0A

The following table lists the subtype codes used in the [[type descriptor]] of the [[refnum data type]].

{| class="wikitable"
|-
! Sub-Type Code
! Refnum Type
! Description
|-
| 0x00
| Generic
| the generic type 0x00 is generated only by getting the TD of the "Not a Refnum Constant".
|-
| 0x01
| Datalog File Refnum
|
|-
| 0x02
| Byte Stream File Refnum
|
|-
| 0x03
| Device Refnum
| used in legacy Serial VIs
|-
| 0x04
| Occurence Refnum
|
|-
| 0x05
| TCP Connection Refnum
|
|-
| 0x06
| VISA Refnum (Obsolete)
| obsolete VISA refnum type up to LabVIEW 5.1
|-
| 0x07
| Automation Refnum
|
|-
| 0x08
| VI Server Refnum
|
|-
| 0x09
| Menu Refnum
|
|-
| 0x0A
| IVI Refnum (Obsolete)
| obsolete IVI refnum type up to LabVIEW 5.1
|-
| 0x0B
| IMAQ Session
|
|-
| 0x0D
| DataSocket Refnum
|
|-
| 0x0E
| VISA Resource
|
|-
| 0x0F
| IVI Logical Name
|
|-
| 0x10
| UDP Connection Refnum
|
|-
| 0x11
| Notifier Refnum
|
|-
| 0x12
| Queue Refnum
|
|-
| 0x13
| IrDA Refnum
|
|-
| 0x14
| Storage Refnum
|
|-
| 0x15
| FieldPoint IO Point/Motion Resource
|
|-
| 0x17
| Event Registration Refnum
|
|-
| 0x18
| .NET Refnum
|
|-
| 0x19
| User Event Refnum
|
|-
| 0x1B
| Event Callback
|
|-
| 0x1F
| Bluetooth Refnum
|
|}

==See Also==
*[[type descriptor]]

Shell Command

2007-05-09T20:03:43Z

Jpdrolet:

The exec VI function can be used to send shell commands. Include the shell call with the commands that are desired. Under Windows 2K/XP/Vista operating systems the call is to '''cmd.exe'''. For example, the string to copy filea to a drive would be
[code]
cmd /C "copy filea a:"
[/code]
with the arguments enclosed in quotes. The exact shell call will depend on the operating system. For Windows 98/ME it is '''command.com'''.

To open a document with its associated application, use the '''start''' command.
[code]
cmd /C "start "" "c:\document.txt"
[/code]
will open ''document.txt'' with Notepad (Windows default).

Shell Command

2007-05-09T20:02:19Z

Jpdrolet:

The exec VI function can be used to send shell commands. Include the shell call with the commands that are desired. Under Windows 2K/XP/Vista operating systems the call is to '''cmd.exe'''. For example, the string to copy filea to a drive would be
[code]
cmd /C "copy filea a:"
[/code]
with the arguments enclosed in quotes. The exact shell call will depend on the operating system. For Windows 98/ME it is ''command.com''.

To open a document with its associated application, use the '''start''' command.
[code]
cmd /C start "" "c:\document.txt"
[/code]
will open ''document.txt'' with Notepad (Windows default).

Custom LabVIEW configuration file

2007-04-04T14:30:33Z

Jpdrolet:

== '''Customize LabVIEW.ini to your project''' ==

''In the following, project has a pre-LabVIEW 8 meaning e.g. a collection of related VIs''

The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

'''Using LabVIEW with a custom ini file'''

- '''Command Line'''
From the command line you have to specify the ini file with the -pref switch:

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "c:\MyProject\labview.ini"

This is not a very convenient method to start LabVIEW.

- '''Shortcuts'''
Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line

- '''Custom file extensions'''
Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "%L"

With this setup you can start LabVIEW with a custom ini file just by double clicking on the lv82ini file of the project. If you work with more than one version of LabVIEW, create one file extension for each version like *.lv80ini and *.lv71ini with actions using the corresponding LabVIEW executable. That allows to conveniently start with the LabVIEW version and the preference file of the project.

Already invoking LabVIEW from a shortcut or an action on a file extension, we can also make the command to run a VI. For example, setting the file extension action to run

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" "c:\tools\lv_start.vi" -pref "%L"

will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).

'''Benefits of a custom ini file'''

- '''Default Path'''
The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.

- '''Browse history'''
The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.

- '''Source Code Control (SCC)'''
Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project.

- '''Other Project dependent Settings'''
Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.

The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.

Custom LabVIEW configuration file

2007-04-04T14:28:47Z

Jpdrolet: /* '''Customize LabVIEW.ini to your project''' */

== '''Customize LabVIEW.ini to your project''' ==

''In the following, project has a pre-LabVIEW 8 meaning e.g. a collection of related VIs''

The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

'''Using LabVIEW with a custom ini file'''

- '''Command Line'''
From the command line you have to specify the ini file with the -pref switch:

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "c:\MyProject\labview.ini"

This is not a very convenient method to start LabVIEW.

- '''Shortcuts'''
Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line

- '''Custom file extensions'''
Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "%L"

With this setup you can start LabVIEW with a custom ini file just by double clicking on the lv82ini file of the project. If you work with more than one version of LabVIEW, create one file extension for each version like *.lv80ini and *.lv71ini with actions using the corresponding LabVIEW executable. That allows to conveniently start with the LabVIEW version and the preference file of the project.

Invoking LabVIEW from a shortcut or an action on a file extension, we can also make the command to run a VI. For example, setting the file extension action to run

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" "c:\tools\lv_start.vi" -pref "%L"

will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).

'''Benefits of a custom ini file'''

- '''Default Path'''
The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.

- '''Browse history'''
The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.

- '''Source Code Control (SCC)'''
Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project.

- '''Other Project dependent Settings'''
Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.

The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.

Custom LabVIEW configuration file

2007-04-04T12:50:03Z

Jpdrolet:

== '''Customize LabVIEW.ini to your project''' ==

''In the following, project has a pre-LabVIEW 8 meaning e.g. a collection of related VIs''

The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

'''Using LabVIEW with a custom ini file'''

- '''Command Line'''
From the command line you have to specify the ini file with the -pref switch:

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe -pref "c:\MyProject\labview.ini"

This is not a very convenient method to start LabVIEW.

- '''Shortcuts'''
Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line

- '''Custom file extensions'''
Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe -pref "%L"

With this setup you can start LabVIEW with a custom ini file just by double clicking on the lv82ini file of the project. If you work with more than one version of LabVIEW, create one file extension for each version like *.lv80ini and *.lv71ini with actions using the corresponding LabVIEW executable. That allows to conveniently start with the LabVIEW version and the preference file of the project.

Invoking LabVIEW from a shortcut or an action on a file extension, we can also make the command to run a VI. For example, setting the file extension action to run

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" "c:\tools\lv_start.vi" -pref "%L"

will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).

'''Benefits of a custom ini file'''

- '''Default Path'''
The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.

- '''Browse history'''
The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.

- '''Source Code Control (SCC)'''
Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project.

- '''Other Project dependent Settings'''
Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.

The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.

Custom LabVIEW configuration file

2007-04-04T12:46:53Z

Jpdrolet:

== '''Customize LabVIEW.ini to your project''' ==

The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

'''Using LabVIEW with a custom ini file'''

- '''Command Line'''
From the command line you have to specify the ini file with the -pref switch:

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe -pref "c:\MyProject\labview.ini"

This is not a very convenient method to start LabVIEW.

- '''Shortcuts'''
Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line

- '''Custom file extensions'''
Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe -pref "%L"

With this setup you can start LabVIEW with a custom ini file just by double clicking on the lv82ini file of the project. If you work with more than one version of LabVIEW, create one file extension for each version like *.lv80ini and *.lv71ini with actions using the corresponding LabVIEW executable. That allows to conveniently start with the LabVIEW version and the preference file of the project.

Invoking LabVIEW from a shortcut or an action on a file extension, we can also make the command to run a VI. For example, setting the file extension action to run

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" "c:\tools\lv_start.vi" -pref "%L"

will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).

'''Benefits of a custom ini file'''

- '''Default Path'''
The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.

- '''Browse history'''
The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.

- '''Source Code Control (SCC)'''
Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project.

- '''Other Project dependent Settings'''
Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.

The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.

Custom LabVIEW configuration file

2007-04-04T12:32:30Z

Jpdrolet: New page: == '''Customize LabVIEW.ini to your project''' == The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default ...

== '''Customize LabVIEW.ini to your project''' ==

The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

'''Using LabVIEW with a custom ini file'''

- '''Command Line'''
From the command line you have to specify the ini file with the -pref switch:

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe -pref "c:\MyProject\labview.ini"

This is not a very convenient method to start LabVIEW.

- '''Shortcuts'''
Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line

- '''Custom file extensions'''
Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:
"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe -pref "%L"
With this setup you can start LabVIEW with a custom ini file just by double clicking on the lv82ini file of the project. If you work with more than one version of LabVIEW, create one file extension for each version like *.lv80ini and *.lv71ini with actions using the corresponding LabVIEW executable. That allows to conveniently start with the LabVIEW version and the preference file of the project.

Invoking LabVIEW from a shortcut or an action on a file extension, we can also make the command to run a VI. For example, setting the file extension action to run

"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" "c:\tools\lv_start.vi" -pref "%L"

will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).

'''Benefits of a custom ini file'''

- '''Default Path'''
The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.

- '''Browse history'''
The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.

- '''Source Code Control (SCC)'''
Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project.

- '''Other Project dependent Settings'''
Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.

The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.

Development Environment

2007-04-04T12:07:50Z

Jpdrolet:

This is the portal for information related to enhancing or modifying the LabVIEW Development environment.

====Pages here:====
*[[How to do Menu Launch VIs]]
*[[Most Recently Used Folders in LV8.20]]
*[[LabVIEW ini File]]
*[[LabVIEW ini Settings]]
*[[LLB]]
*[[Multiple Instances of LabVIEW]]
*[[VI Icons]]
*[[Insane Objects]]