Labview ini file syntax

Hi
I have a ini file built into an application as a support file. When I did some changes on ini file, some change was reflected in executable file but some not. I suspect the syntax in ini file are not right so aren't recognized.
Besides, how ini file works? when I change the ini file, do I have to re-execute the application in order to getting the reflection in application? Or if the configuration is changed via the menu Tools->option in application, will they rewrite the ini file automatically? Do I have to stop the application in order to reading a changed ini file?
Where can I find a documentation about labview ini file as well as its syntax?
Thanks.

An .ini file is a standard file and is not something that is special to LabVIEW. LabVIEW itself uses an .ini file to store some application settings that you change via the Tools->Options menu. It is not wise to change this file yourself manually. You can create your own .ini files for your application. You can use the VIs in the Configration File VIs palette to read/write .ini files. This palette is a sub-palette from the File I/O palette.
As for its format, it's made up of sections and keys like this:
[Section1]
keyname=value
keyname=value
[Section2]
keyname=value
;this is a comment
If the value you're trying to save is a string you should use quotes.
What you store in the .ini file is up to you and how you use it is also up to you. You can access the keys on an as-needed basis, or you can read the keys in at the beginning of your program, store them someplace like a global variable and access them as needed. It's kind of dependent on the size and architecture of your application.

Similar Messages

We want your LabVIEW INI files!

Hello:
As some of you might know, the Tools>>Options dialog box allows you to control options that are stored in the LabVIEW.INI file. With each release of LabVIEW, we have steadily increased the number of available options to customize LabVIEW environment. For example, the LabVIEW R&D team has added over 15 block diagram options since LabVIEW 5.x and only removed a small handful.
As the LabVIEW team introduces new features, we provide more and more configurable options to satisfy different development styles or interests. However, the proliferation of options can prove confusing. It becomes difficult to distinguish between widely-used options and ones that are applicable only to a small set of customers.
To gain a better sense of how customers use the settings in the Tools>>Options dialog box, I would like to collect as many customer INI files as possible. This will allow me to analyze option usage and improve the usability of the Tools>>Options dialog box.
Please help by sending your INI file(s) to the following email address along with answers to a few simple questions. The more INI files, the better. Therefore, encourage your colleagues to send their INI files, too! If you are a MacOS or Linux user, attach your LabVIEW Preferences or .labviewrc file. I'm interested in receiving INI files from users of all experience levels -- novice, intermediate, advanced!
Send to: [email protected]
What is the first version of LabVIEW that you used?
When upgrading to a new version of LabVIEW, do you copy the LabVIEW.INI file from the older version of LabVIEW to the newer version of LabVIEW?
When launching a new version of LabVIEW, do you immediately change any particular settings in the Tools>>Options dialog box? If so, which ones?
When upgrading to a new version of LabVIEW, do you review the New and Changed page in the Tools>>Options dialog box?
Which options are you the most passionate about? Please provide a brief reason for each.
Do you have any suggestions to improve the usability of the Tools>>Options dialog box?
Please do not forget to attach your LabVIEW.INI file.
Note: On Windows the LabVIEW.INI file resides next to the LabVIEW.exe. On Mac OS, your options are stored in the LabVIEW Preferences text file in the System: Preferences folder. On Linux, the .labviewrc file is in your home directory.
Thank you,
Noel Adorno
LabVIEW R&D

Hai noel,
Its great and delighting to hear that LabVIEW R&D team is in an constant effort in collecting the information about user experience and appropriate changes are done. Each enhancment or feature inclusion that is done to LabVIEW makes the users more comfortable with the environment and kindles the user for new version LabVIEW experience...
Hats off to LabVIEW R&D team.
With regards,
JK
(Certified LabVIEW Developer)
Give Kudos for Good Answers, and Mark it a solution if your problem is solved.

Labview.ini and graph rescaling

Hi everyone,
I'm using Labview 71. and 8.0 on Mac OSX.
It used to be (under Laview 6) that to disable graph rescaling a one line labview.ini file would do the job. The one line would be
EnableAutoScales=False
See for example
http://zone.ni.com/devzone/cda/tut/p/id/3815
This would work if you put the labview.ini file in the same directory as the Labview application.
Now, with Labviews 7 and 8, its not working anymore, well at least not for me.
Has the name of the file changed? (Does its capitalization matter?) Has it been superceeded by some other mechanism?
Exactly where should the file be? (Mine is in bootdrive:Applications:National Instruments:Labview 7.1
Has the syntax of labview.ini changed? (Is that single line sufficient?)
I noticed that the valuable web page discussing INI files, labview.brianrenken.com/ini, is not working right now.
Thanks in advance,
Peter H.

PGH wrote:
It used to be (under Laview 6) that to disable graph rescaling a one line labview.ini file would do the job. The one line would be
EnableAutoScales=False
Now, with Labviews 7 and 8, its not working anymore, well at least not for me.
I think that the the global .ini entry EnableAutoScales=False disappeared from use as of LV6.1 when it was replaced with the ability to right-click (or do the Mac equivalent) on individual graphs and toggle Advanced>Auto Adjust Scales.
=====================================================
Fading out. " ... J. Arthur Rank on gong."

Labview.ini

Hello,
How can I do to have each user its own labview.ini file ? And of course bee able to edit it.
I first copy a file labview.ini into a "home" directory and use a shortcut which is supposed to start Labview from
the same "home" directory, But still Labview does not use it. I probably need to change something else maybe in the regedit.
Thank

From the online Help:
LabVIEW stores options in a labview.ini file in the LabVIEW directory. The file format is similar to other .ini files. It begins with a LabVIEW section marker followed by the option name and the values, such as offscreenUpdates=True.
If you want to use a different options file, specify
the file in the shortcut you use to start LabVIEW. For example, to use
an options file on your computer named lvrc instead of labview.ini, right-click the LabVIEW icon on the desktop and select Properties. Click the Shortcut tab and type labview -pref lvrc in the Target text box.

What options can be in a labview created .exe's .ini file?

Every executable created by labview has a .ini file associated with it. What options can I enter into this file?. I was told that entering a section with the name of the executable and HideMainWindow=True would stop 2 entries being made in the system tray. I either didn't understand or it doesn't work. I am wondering where can I find a documented list of entries that can be made in the .ini file?
Thanks in advance. Any help would be appreciated.
Bob

For the keys to work they need to be in a section that has the same name as the executable. For instance, the program MyApp.exe might have a MyApp.ini file containing something like:
[MyApp]
hideRootWindow=true
Mike...
PS: it also helps of you have the name of the key right...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Labview Read INI File Slow

Dear ALL:
I have a VI use OpenG Read INI Cluster subvi to read a complex cluster data structure called step config data,and when I Run this VI,It sometimes read INI File quickly,and sometimes read INI File very slowly.If I want to speed up the read INI File speed,I must quit labview and restart it,and when I quit labview it will reports error just look like Labview Error Message.JPG
Attachments:
Labview Error Message.JPG ‏18 KB
Data Structure.JPG ‏92 KB
Get Data VI.JPG ‏189 KB

I've got the same problem - it takes from 4 to 20 SECONDS to write and read 2 ini file clusters.
The first cluster I write have a few text strings, an error cluster and some numbers.
The second is an array of clusters (I loop through the array and writes each cluster separately.) containing some text and numbers, most of it contained in sub-clusters.
With 0 or 1 element in the array it takes around 4 secs to write and read this to ini file. With 20 in the cluster this takes 20 seconds (on a cFP-2120).
The openG functionality here is quite nice, but if I can't fix this time problem I'm afraid its quite useless!
Attachments:
WriteINIFile.jpg ‏211 KB
IniCluster.jpg ‏114 KB

Syntax error in NQSConfig.ini.file

# NQSConfig.INI
# Copyright (c) 1997-2006 Oracle Corporation, All rights reserved
# INI file parser rules are:
# If values are in literals, digits or _, they can be
# given as such. If values contain characters other than
# literals, digits or _, values must be given in quotes.
# Repository Section
# Repositories are defined as logical repository name - file name
# pairs. ODBC drivers use logical repository name defined in this
# section.
# All repositories must reside in OracleBI\server\Repository
# directory, where OracleBI is the directory in which the Oracle BI
# Server software is installed.
[ REPOSITORY ]
Star     =     OracleBIAnalyticsApps.rpd, DEFAULT
# Query Result Cache Section
[ CACHE ]
ENABLE     =     NO;
// A comma separated list of <directory maxSize> pair(s)
// e.g. DATA_STORAGE_PATHS = "d:\OracleBIData\nQSCache" 500 MB;
DATA_STORAGE_PATHS     =     "C:\OracleBIData\cache" 500 MB;
MAX_ROWS_PER_CACHE_ENTRY = 100000; // 0 is unlimited size
MAX_CACHE_ENTRY_SIZE = 1 MB;
MAX_CACHE_ENTRIES = 1000;
POPULATE_AGGREGATE_ROLLUP_HITS = NO;
USE_ADVANCED_HIT_DETECTION = NO;
MAX_SUBEXPR_SEARCH_DEPTH = 7;
// Cluster-aware cache
// GLOBAL_CACHE_STORAGE_PATH = "<directory name>" SIZE;
// MAX_GLOBAL_CACHE_ENTRIES = 1000;
// CACHE_POLL_SECONDS = 300;
// CLUSTER_AWARE_CACHE_LOGGING = NO;
# General Section
# Contains general server default parameters, including localization
# and internationalization, temporary space and memory allocation,
# and other default parameters used to determine how data is returned
# from the server to a client.
[ GENERAL ]
// Localization/Internationalization parameters.
LOCALE     =     "English-usa";
SORT_ORDER_LOCALE     =     "English-usa";
SORT_TYPE = "binary";
// Case sensitivity should be set to match the remote
// target database.
CASE_SENSITIVE_CHARACTER_COMPARISON = OFF ;
// SQLServer65 sorts nulls first, whereas Oracle sorts
// nulls last. This ini file property should conform to
// that of the remote target database, if there is a
// single remote database. Otherwise, choose the order
// that matches the predominant database (i.e. on the
// basis of data volume, frequency of access, sort
// performance, network bandwidth).
NULL_VALUES_SORT_FIRST = OFF;
DATE_TIME_DISPLAY_FORMAT = "yyyy/mm/dd hh:mi:ss" ;
DATE_DISPLAY_FORMAT = "yyyy/mm/dd" ;
TIME_DISPLAY_FORMAT = "hh:mi:ss" ;
// Temporary space, memory, and resource allocation
// parameters.
// You may use KB, MB for memory size.
WORK_DIRECTORY_PATHS     =     "C:\OracleBIData\tmp";
SORT_MEMORY_SIZE = 4 MB ;
SORT_BUFFER_INCREMENT_SIZE = 256 KB ;
VIRTUAL_TABLE_PAGE_SIZE = 128 KB ;
// Analytics Server will return all month and day names as three
// letter abbreviations (e.g., "Jan", "Feb", "Sat", "Sun").
// To use complete names, set the following values to YES.
USE_LONG_MONTH_NAMES = NO;
USE_LONG_DAY_NAMES = NO;
UPPERCASE_USERNAME_FOR_INITBLOCK = NO ; // default is no
// Aggregate Persistence defaults
// The prefix must be between 1 and 8 characters long
// and should not have any special characters ('_' is allowed).
AGGREGATE_PREFIX = "SA_" ;
# Security Section
# Legal value for DEFAULT_PRIVILEGES are:
# NONE READ
[ SECURITY ]
DEFAULT_PRIVILEGES = READ;
PROJECT_INACCESSIBLE_COLUMN_AS_NULL     =     NO;
MINIMUM_PASSWORD_LENGTH     =     0;
#IGNORE_LDAP_PWD_EXPIRY_WARNING = NO; // default is no.
#SSL=NO;
#SSL_CERTIFICATE_FILE="servercert.pem";
#SSL_PRIVATE_KEY_FILE="serverkey.pem";
#SSL_PK_PASSPHRASE_FILE="serverpwd.txt";
#SSL_PK_PASSPHRASE_PROGRAM="sitepwd.exe";
#SSL_VERIFY_PEER=NO;
#SSL_CA_CERTIFICATE_DIR="CACertDIR";
#SSL_CA_CERTIFICATE_FILE="CACertFile";
#SSL_TRUSTED_PEER_DNS="";
#SSL_CERT_VERIFICATION_DEPTH=9;
#SSL_CIPHER_LIST="";
# There are 3 types of authentication. The default is NQS
# You can select only one of them
#----- 1 -----
#AUTHENTICATION_TYPE = NQS; // optional and default
#----- 2 -----
#AUTHENTICATION_TYPE = DATABASE;
# [ DATABASE ]
# DATABASE = "some_data_base";
#----- 3 -----
#AUTHENTICATION_TYPE = BYPASS_NQS;
# Server Section
[ SERVER ]
SERVER_NAME = Oracle_BI_Server ;
READ_ONLY_MODE = NO;     // default is "NO". That is, repositories can be edited online.
MAX_SESSION_LIMIT = 2000 ;
MAX_REQUEST_PER_SESSION_LIMIT = 500 ;
SERVER_THREAD_RANGE = 40-100;
SERVER_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
DB_GATEWAY_THREAD_RANGE = 40-200;
DB_GATEWAY_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
MAX_EXPANDED_SUBQUERY_PREDICATES = 8192; // default is 8192
MAX_QUERY_PLAN_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_INFO_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_QUERY_CACHE_ENTRIES = 1024; // default is 1024
INIT_BLOCK_CACHE_ENTRIES = 20; // default is 20
CLIENT_MGMT_THREADS_MAX = 5; // default is 5
# The port number specified with RPC_SERVICE_OR_PORT will NOT be considered if
# a port number is specified in SERVER_HOSTNAME_OR_IP_ADDRESSES.
RPC_SERVICE_OR_PORT = 9703; // default is 9703
# If port is not specified with a host name or IP in the following option, the port
# number specified at RPC_SERVICE_OR_PORT will be considered.
# When port number is specified, it will override the one specified with
# RPC_SERVICE_OR_PORT.
SERVER_HOSTNAME_OR_IP_ADDRESSES = "ALLNICS"; # Example: "hostname" or "hostname":port
# or "IP1","IP2":port or
# "hostname":port,"IP":port2.
# Note: When this option is active,
# CLUSTER_PARTICIPANT should be set to NO.
ENABLE_DB_HINTS = YES; // default is yes
PREVENT_DIVIDE_BY_ZERO = YES;
CLUSTER_PARTICIPANT = NO; # If this is set to "YES", comment out
# SERVER_HOSTNAME_OR_IP_ADDRESSES. No specific NIC support
# for the cluster participant yet.
// Following required if CLUSTER_PARTICIPANT = YES
#REPOSITORY_PUBLISHING_DIRECTORY = "<dirname>";
#REQUIRE_PUBLISHING_DIRECTORY = YES; // Don't join cluster if directory not accessible
DISCONNECTED = NO;
AUTOMATIC_RESTART = YES;
# Dynamic Library Section
# The dynamic libraries specified in this section
# are categorized by the CLI they support.
[ DB_DYNAMIC_LIBRARY ]
ODBC200 = nqsdbgatewayodbc;
ODBC350 = nqsdbgatewayodbc35;
OCI7 = nqsdbgatewayoci7;
OCI8 = nqsdbgatewayoci8;
OCI8i = nqsdbgatewayoci8i;
OCI10g = nqsdbgatewayoci10g;
DB2CLI = nqsdbgatewaydb2cli;
DB2CLI35 = nqsdbgatewaydb2cli35;
NQSXML = nqsdbgatewayxml;
XMLA = nqsdbgatewayxmla;
ESSBASE = nqsdbgatewayessbasecapi;
# User Log Section
# The user log NQQuery.log is kept in the server\log directory. It logs
# activity about queries when enabled for a user. Entries can be
# viewed using a text editor or the nQLogViewer executable.
[ USER_LOG ]
USER_LOG_FILE_SIZE = 10 MB; // default size
CODE_PAGE = "UTF8"; // ANSI, UTF8, 1252, etc.
# Usage Tracking Section
# Collect usage statistics on each logical query submitted to the
# server.
[ USAGE_TRACKING ]
ENABLE = YES;
//==============================================================================
// Parameters used for writing data to a flat file (i.e. DIRECT_INSERT = NO).
STORAGE_DIRECTORY = "<full directory path>";
CHECKPOINT_INTERVAL_MINUTES = 5;
FILE_ROLLOVER_INTERVAL_MINUTES = 30;
CODE_PAGE = "ANSI"; // ANSI, UTF8, 1252, etc.
//==============================================================================
DIRECT_INSERT = YES;
//==============================================================================
// Parameters used for inserting data into a table (i.e. DIRECT_INSERT = YES).
PHYSICAL_TABLE_NAME = "OBI Usage Tracking"."Catalog"."dbo"."S_NQ_ACCT" ; // Or "<Database>"."<Schema>"."<Table>" ;
CONNECTION_POOL = "OBI Usage Tracking"."Usage Tracking Writer Connection Pool>" ;
BUFFER_SIZE = 10 MB ;
BUFFER_TIME_LIMIT_SECONDS = 5 ;
NUM_INSERT_THREADS = 5 ;
MAX_INSERTS_PER_TRANSACTION = 1 ;
//==============================================================================
# Query Optimization Flags
[ OPTIMIZATION_FLAGS ]
STRONG_DATETIME_TYPE_CHECKING = ON ;
# CubeViews Section
[ CUBE_VIEWS ]
DISTINCT_COUNT_SUPPORTED = NO ;
STATISTICAL_FUNCTIONS_SUPPORTED = NO ;
USE_SCHEMA_NAME = YES ;
USE_SCHEMA_NAME_FROM_RPD = YES ;
DEFAULT_SCHEMA_NAME = "ORACLE";
CUBE_VIEWS_SCHEMA_NAME = "ORACLE";
LOG_FAILURES = YES ;
LOG_SUCCESS = NO ;
LOG_FILE_NAME     =     "C:\OracleBI\server\Log\CubeViews.Log";
# MDX Member Name Cache Section
# Cache subsystem for mapping between unique name and caption of
# members for all SAP/BW cubes in the repository.
[ MDX_MEMBER_CACHE ]
// The entry to indicate if the feature is enabled or not, by default it is NO since this only applies to SAP/BW cubes
ENABLE = NO ;
// The path to the location where cache will be persisted, only applied to a single location,
// the number at the end indicates the capacity of the storage. When the feature is enabled,
// administrator needs to replace the "<full directory path>" with a valid path,
// e.g. DATA_STORAGE_PATH = "C:\OracleBI\server\Data\Temp\Cache" 500 MB ;
DATA_STORAGE_PATH     =     "C:\OracleBIData\cache" 500 MB;
// Maximum disk space allowed for each user;
MAX_SIZE_PER_USER = 100 MB ;
// Maximum number of members in a level will be able to be persisted to disk
MAX_MEMBER_PER_LEVEL = 1000 ;
// Maximum size for each individual cache entry size
MAX_CACHE_SIZE = 100 MB ;
# Oracle Dimension Export Section
[ ORA_DIM_EXPORT ]
USE_SCHEMA_NAME_FROM_RPD = YES ; # NO
DEFAULT_SCHEMA_NAME = "ORACLE";
ORA_DIM_SCHEMA_NAME = "ORACLE";
LOGGING = ON ; # OFF, DEBUG
LOG_FILE_NAME     =     "C:\OracleBI\server\Log\OraDimExp.Log";
Help me out Gurus thanks in advance

Hi,
Star = OracleBIAnalyticsApps.rpd, DEFAULTthis should be end with semicolon
Star = OracleBIAnalyticsApps.rpd, DEFAULT;
Assign Points and close thread, if your question is answered...
Cheers,
Aravind

.INI files vs .TXT files for changing default values in a .EXE?

Hi,
I have a two-part question related to updating the default values of controls in an executable:
I am creating a LabVIEW executable for installation on two different production-floor computers.   I need to be able to change the default values of the front panel controls (as I would do with the “make this value default” command during development). From reading prior posts, I understand that I could use the “Write Configuration Settings File.vi” and “Read Configuration Settings File.vi” to generate a .INI file that would be read by the .EXE and would establish the desired values of the controls. However when I took a look at the block diagrams for those configuration .VIs, they don’t appear (to me) to be any easier to use than just reading values from a spreadsheet file. IE: Instead of using these configuration files and a .INI file, could I not instead just read values from a .TXT file that contains the desired values?   I’ve never used a .INI file before, or had to worry about “keys” and “sections,” so from my (perhaps naïve) perspective, the .INI method seems less easy to use. Is there any advantage to the .INI format?
Regardless of whether I use the .INI file or a .TXT file, I have this additional problem: One of the things that changes when I install my .EXE file on a new computer is the COM port numbers used by two serial devices.   (On my development computer, the two serial devices use COM5 and COM6, whereas on the two production-flood computers, the COM ports will almost certainly be different).   I suppose I could use the Device Manager on the production-floor computers to change the COM ports to be the same as those on my development computer, but I’d prefer to be able to (again) change the default value of the COM ports in my .EXE.   However, I’m not sure how to do that.   The configuration VIs, have options for reading / writing Booleans, strings, paths, and numeric, but not, (so far as I can tell) for a VISA class.
Any thoughts / suggestions are welcome. Thanks.
Solved!
Go to Solution.

Dan_the_Clam wrote:
Thanks for your reply, Yamaeda,
Great that I can use a string to open a VISA session - I had no idea. I'll try that.
And - ah - you are right about the .INI files. I just did an experiment in which I re-ordered the sections and randomly changed which letters were capitalized in the key values, and the "read configuration settings.VI" still read the file correctly. Thanks for that.
Unfortunately, in my existing code, the controls on the block-diagram aren't all co-located together; they are scattered throughout the block diagram - some of them in case structures and loops.   I suppose that means I'll have to move them all to the left side of the block diagram, route them to these "Write Key.VIs" and then wire them up into the cases and loops with fairly long wires.   It's just a hassle, and is going to make my block diagram more complicated.  Well, I suppose that's how one learns...
Thanks again.
dan
Assuming you have a state machine and an Init state it's a fair use of Local Variables to update controls from the ini-file. The same goes for saving the values.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Why is the .ini file deleted by iteself?

Hi all,
I am working on a large program. It is really large and messy, but it works. The problem is sometimes it deletes .ini file by itself. This program uses a .ini file to keep all kinds of configurations. Sometimes when the program exits, it causes the computer to reboot -- even worse, at same time it deletes the .ini file......who can tell me the possible reasons?
Thanks!

Hi steady,
Does your program use the LabVIEW configuration file VIs to maintain its own INI file? In LabVIEW 7.1, I think the Close Config Data VI used to write the data back to the INI file by default even when nothing changed. Try setting "write configuration data?" to false when you call that VI.
Do you have any more information about the reboot? It may be a system crash caused by a device driver. Why Does My Computer Automatically Reboot For No Reason? explains how to obtain more information about system crashes.
Brad
Brad Keryan
NI R&D

Modification to Write Configuration .ini file

I have found one of the annoying things about Labview's configuration file VI's is that when the configuration file is written, all spacing between sections is eliminated making it hard to read, even if the spacing was there to begin with when the file was read. For example, I would like the file to look like
[Header1]
key1=value1
key2=value2
[Header2]
key3=value3
key4=value4
But it comes out looking like:
[Header1]
key1=value1
key2=value2
[Header2]
key3=value3
key4=value4
making it harder to read.
I made a modification to the file Config Data to String.vi which is located \vi.lib\UTILITY\config.llb\
Make a backup copy of \vi.lib\UTILITY\config.llb\Config Data to String.vi and replace the file in the config.llb with the attachment (saved as LV 8.0).
What I did was any time a section header is to be written to the file, I preceded it with another CRLF character so that it creates a blank line just before the section header. To keep from having an extra blank line at the beginning of the .ini file, it does not create the CRLF there.
I hope others will find this modification useful.
Attachments:
Config Data to String.vi ‏26 KB

tst wrote:
The idea itself is great, but I don't like the idea of changing vi.lib files (for several reasons).
I didn't look at your code, but I assume that at least in this case, the resulting files will still be processed fine by machines which don't have this modification, so it's probably not as bad, but I still don't like it.
You should probably go to the Product Suggestion Center and tell NI about this idea.
I agree about not trying to change the vi.lib files. It gets into modifying code that is rather deeply embedded about 3 or 4 sub-vi's down. By my testing, machines without the modification do handle the files just fine. The alternative would be to create a backup copy of the whole library and rename the files and use my own versions instead. I've recently installed the OpenG files and looked into them. I like the functionality they provide to be able to store and retrieve clusters of configuration data. Of course they have NI's write configuration files at the heart as well, so if they link to the original VI library then they will generate the same .ini files missing the extra lines that I like.
tst wrote:
You should probably go to the Product Suggestion Center and tell NI about this idea.
Thanks, I already did this some time ago when I created a test VI to just read and close an .ini file. I found that without setting the "write configuration file" flag in the close config file VI (which defaults to True), the whole file got rewritten even though nothing had changed. That's how I stumbled across this loss of blank lines thing.
I hope NI will look into that suggestion and add it to the config file VI library in the future. It would probably need to be implemented with a flag that says "Add blank lines?" that would default to False so that the original behavior of the VI could be maintained. Since the VI that controls the appearance of the file is a few layers deeper than Close config file VI, that flag would have to be passed through a couple of sub-VI's.
Thanks for your feedback.
Message Edited by Ravens Fan on 09-22-2007 03:22 PM

Using ini-files with write-key/read-key (double) and defined accurarcy

Hello,
in a popup the user can insert a numeric-double-value.
This value is saved in a ini-file using the Write-key-vi with Type = double. Works fine.
What do i have to do to set the values after the comma?
So if user inserts 1,532 i want to round to two digits after comma and save it. (-> 1,53)
Thx
Solved!
Go to Solution.

I don't know how LV deals with different decimal seperators (e.g. comma instead of point), I guess it 'just works' depending on the system locale.
A few different options are available as follows...
The Write Key function has a 'precision' input which will set the number of decimal places to save the DBL to (in your case, set this to 2):
If you are using a numeric field, you can set the 'increment' property with 'coerce to nearest' to prevent them from entering more precision than is available:
The obvious method for post-rounding the input is to scale up the number, round to the nearest integer and then divide again to limit the precision:
I couldn't see anything in the numeric/math palettes that does this.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Why vi dll creates ini file on its own?

Hello,
I have built my LabVIEW project as shared library (dll).
My system looks like this: main exe file loads dll, and this dll loads VI dll.
With LabVIEW 2011 it was ok, but when I switched to 2013 my VI dll started to write into main exe ini file.
When dll is loaded those lines appears in main exe ini file:
[LVRT]
RTTarget.ApplicationPath=C:\Users\user\Documents\LabVIEW Data\Remote Development\startup.rtexe
RTTarget.VIPath=C:\Users\user\Documents\LabVIEW Data\Remote Development
Does someone know what causes this and how to turn it off?

I got the same thing when I built an exe. I have a custom INI file, it has the following entries:
[Oscilloscope 2013]
server.app.propertiesEnabled=True
server.tcp.serviceName="My Computer/VI Server"
server.vi.propertiesEnabled=True
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
DebugServerEnabled=False
DebugServerWaitOnLaunch=True
FPFont="Segoe UI" 15
appFont="Segoe UI" 15
dialogFont="Segoe UI" 15
systemFont="Segoe UI" 15
BDFont="Segoe UI" 15
The only dll it calls is lvanlys.dll. After running the EXE the following are appending to the INI file
RTTarget.ApplicationPath=C:\Users\XXX\Documents\LabVIEW Data\Remote Development\startup.rtexe
RTTarget.VIPath=C:\Users\XXX\Documents\LabVIEW Data\Remote Development
Regards,
mcduff

How to create a comment in config.ini file

Does anyone know how to create a comment line in the Essbase config.ini file (server config file, not client, if they are different)?I know that for ESSCMD it is :Calcs it is /*but not sure of syntax for commenting config files. Thanks in advance!

The comment character for the essbase.cfg file (I assume that is what you are talking about) is a semi-colon (;)Regards,Jade-----------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

How to create table from .ini file

Hi,
The file *.ini generates a Multicolumn Listbox where is indicated a number (variable) of tables with them characteristics (row and column) as in the picture below.
I need to find the way to create automatically, on word file, the tables as indicated in the *.ini file. Do you think that it could be possible? That you know, exist a Macro to do this?
Best regards
Attachments:
Multicolunms .png ‏8 KB

As Taki said above, to do this you need to use the Report Generation Toolkit. This will allow you to generate tables in a word document. Look for the examples in the LabVIEW Help for a rough idea of how to use the toolkit and if you have any specific questions after that then feel free to post them here.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

What are the options in the application builder application.ini file

What are the options that I can add in the application.ini file that is created by the application builder.

They are about the same as LabVIEW.ini. Scott Hannahs has a list of ini settings for several versions of LabVIEW that can be found here.

Labview ini file syntax

Similar Messages

Maybe you are looking for