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.

Similar Messages

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.

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.

Editing Executable's INI file with "HideRootWindow"

Hello
I'm trying to create an executable so that it shows only one window in the taskbar. On one of the Knowledgebase articles (http://digital.ni.com/public.nsf/allkb/6E660558F3D420C786256FCB005B4F52) I had read about setting HideRootWindow=True in the INI file. I did and it worked. The problem though is that everytime I rebuild the exe in LabVIEW, the line disappears & I have to manually edit the INI file each time. I was wondering if there was anyway I could do it automatically though LabVIEW so that it itself appends that line to INI file at each Build process.
Appreciate any help. Thank you!
Solved!
Go to Solution.

Instead of checking Use the default LabVIEW Configuration file, uncheck this option and add your own ini file. Also make sure that you add the ini file to the Project too! This will help in maintenance.
Hope this helps.

Visual c++ load .ini files to combobox

I create pop up program for my company, I use Visual c++ CLR. I use .ini files for load and write data in my program.
than I have confuse when I want to load .ini files to show in combobox. I already use "GetPrivateProfileStringA/WritePrivateProfileStringA", but it can't read .ini files to combobox. please give my suggestion for my program. thank you (:

Hi,
Welcome to MSDN.
I found that you have posted this issue with the following thread in C++ forum.
Visual
c++ load .ini files to combobox
You could focus on that thread to get support.
Have a nice day.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Import ini file and regfile

I want to import ini file and a reg file at runtime.
Now i know that you can do that with startup shim DLL.
I got sample project for the startup shim but I am not good in c++ programming.
Has somebody example code for import of ini file and reg file.
Please help me......I am stupid

stonehill1957,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Translat.ini File

We are upgrading RP11.3 to RP11.5. We have a number of custom rules that have been merged into 11.5 batch system. The issue we are having is that after we merged our custom error messages for our custom rules into the translate.ini file, the system is not recognizing our entries. It seems that the 11.5 system is pulling these error messages from another file.
How can we get the system to recognize our custom errors messages in translate.ini that we have created and used in past version of Documaker.

Under 11.5, Documaker uses Oracle's globalization standards for messaging. The translat.ini file isn't strictly used at runtime, rather, a compiled binary version that is language-specific is used instead. To generate the compiled binary version, there are some steps to be followed.
The first thing you will need is the LMSGEN utility from Oracle's NLSRTL package. Currently this is distributed with Oracle database SDKs. I don't have any more specific information than that right now. Here is a bit more info on this utility http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch10oci.htm#i1007610
Once you have LMSGEN installed and ready, you need to convert your translat.ini into an intermediary MSG and MMP files. You can create a script that will translate your translat.ini file and create these files for you. It's a relatively simple process:
Translat.ini lines:
1000 = &E&: Error: Requested library <&LIB&> not available or cannot be loaded.
1001 = &E&: Error: Use of rule or function <&NAME&> requires a printer classification of <&CLASS&>.
Translat.msg:
#CHARACTER_SET_NAME=AMERICAN_AMERICA.US7ASCII
1000, 42, "%1: Error: Requested library <%2> not available or cannot be loaded."
1001, 42, "%1: Error: Use of rule or function <%2> requires a printer classification of <%3>."
Translat.mmp:
1000:E,LIB,
1001:E,NAME,CLASS,
The MMP file is a token/parameter mapping file, since the old translat.ini uses tokens, and Oracle's globalization framework uses parameters. Note the top line in the translat.msg file -- this is required!
The format of the INI file:
msgNumber = &TOKEN&: Message with &TOKEN&
The format of the MSG file:
msgNumber, msgType [42=Error,0=Info], "Message with %1 parms"
Format of the MMP file:
msgNumber:TOKEN1,TOKENn,...,
Once you have the MSG file, then use the LMSGEN utility from Oracle's NLSRTL package to converts that into an MSB file. The MSB file is a compiled binary version of the message file, and this is what is used to generate the actual messages. There will be a different MSG file for each language your system should support. In addition, the MSB files are platform dependent and must be compiled on the platform where they are intended to be used.
One thing to keep in mind when running it is that Oracle's messaging libraries are built around the notion of each product having its own separate directory under the Oracle home directory (identified by the ORACLE_HOME environment variable). Each product may in turn have its own separate component or "facility" with its own set of message files. Oracle manages this by having a separate directory under ORACLE_HOME for each product, and then a "mesg" directory under that where the message files for every component are placed. When you run the lmsgen utility, it already expects there to be an Oracle base directory and an ORACLE_HOME environment variable that points to it. In addition it expects there to be a sub-directory for the product under the Oracle directory, and a "mesg" subdirectory under the product directory. When you run the lmsgen routine, it expects you to give it the name of the msg file, the name of the product, and the name of the facility. It uses the product name to locate the "mesg" subdirectory, and it uses the "facility" name as the base name of the msb file that it generates (the filename is suffixed by the language). So, to run lmsgen you will need to have a directory which has some directory underneath with a "mesg" directory under it. So for example (assuming you don't have Oracle code already installed somewhere) you could do the following:
mkdir C:\Documaker\mesg
set ORACLE_HOME=C:\
lmsgen translat.msg Documaker xlt
and lmsgen would write a file name "xltus.msb" to the "C:\Documaker\mesg" directory. (The msg file has a code in the first line identifying the language that it is written in, which is how it knows to name it with a suffix of "us". Documaker currently doesn't use the "ORACLE_HOME" method of locating the file, but as far as I know, you do need to have an ORACLE_HOME defined to run lmsgen.exe.
Since we don't use the ORACLE_HOME method, you would need to provide command-line options to override input and output paths.
lmsgen translat.msg Documaker xlt us -i .\ -o .\
The -i identifies the input directory to location the MSG file. The -o indicates the output directory to use as a destination for the compiled MSB file.
Finally, move the MSB and MMP file to the \dll\lang folder inside your Documaker installation.

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."

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

Want to lesen PDF file in labview

i want tranfer a PDF file to binary String. And store the string in a oracle datebase. First of all, how can i lesen the PDF file use labview?

Portable Document Format, short pdf, is (in general) an open file format. You can find information about this here.
So if you can open the file at all depends on if it is encrypted or not (see usage restriction). Another point is that the text you are reading in a pdf-reader is not stored in the pdf like in any other ASCII-file. There are formatstrings, imagelinks (and data) and other things included WITHIN your text. Afaik (short for "as far as i know"), there are no "preprogrammed" pdf-reader available in LabVIEW, but maybe someone else knows a little more about that.
So if there isn't one, you can only write a pdf-parser on your own......
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

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

I loaded Mac OS X v10.7 Lion yesterday. Everything's running fine, except for a simple problem. Any time I want to copy a file, JPEG, etc., I am prompted "Finder wants to make changes. Type your password to allow this." I don't want this!! Is there a way

I loaded Mac OS X v10.7 Lion yesterday. Everything’s running fine, except for a simple problem. Any time I want to copy a file, JPEG, etc., I am prompted “Finder wants to make changes. Type your password to allow this.” I don’t want this!! Is there a way to unlock “Finder” or rid this process?

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. You can demote it back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:20 ~ $_ ; chmod -R -N ~ $_ 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

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

Read ini file with multiple threads

I have a state machine architecture, but I have multiple threads. For instance, one is dealing with listening for mulitple tcp connections and storing their refnums to an array in a functional global. Another thread is accessing these refnums and collecting data it's receiving from each tcp connection. This data is queued up and then dequeued in a third thread which does some modification and sends it out via serial. My question is, when you have a situation like this and have to read an ini file, where should you read it? It seems like the most logical place would be outside your loops so you can get all the tcp and serial info (port, baud rate, etc) then wire it it to your create listener or initialize serial connection despite them being in different threads. But then again, normal state machine architecture would want an "initialize" case. If you did this though which loop would you put the init case in? And you would then have to worry about synchronizing loops becuase you wouldn't want one to try and create a listener while another thread was still reading ini data which would include the port to listen on. Maybe I'm overthinking this haha. Suggestions? Edit: one more question. Does it seem overkill that I have a tcp loop listening for data and queuing it up and a separate loop sending out the processed data via serial? Or should I just have one state that gets tcp data stores it in a shift register, then another state that sends it out via serial, and returns the state machine to the tcp read state?
Message Edited by for(imstuck) on 03-03-2010 01:13 PM
Message Edited by for(imstuck) on 03-03-2010 01:17 PM
CLA, LabVIEW Versions 2010-2013

Most of the applications I work on at the moment are used for testing barcode and label printers. The test applications I design are focused on testing the printer's firmware, not the hardware. Within our applications we have three primary objects (Unfortunately they are not native LabVIEW objects yet. They were developed before native LVOOP.) The primary objects we use in our applications are a log object, a connection object (communication interface to the printer) and a printer object. In any single instance of a test we only have a single printer, a single connection to the printer and one or more discrete logs. Each instance of these objects represent a single, real physical entity. A singleton object is a virtual representation of the physical world. Let's take the log object since that is the most simple of the objects described above. Naturally for a given log file you have the log file name and path. We also provide other attributes such as the maximum size of a single file (we allow log files to span multiple files), whether it is a comma delimited file or if it contains raw data, if timestamps should be included with a log entry and so forth. Most of these attributes are static for a log file with the exception of the name and such things as whether the logging is actually enabled or disabled. If we split a wire and had multiple instances of the log file (the way native LVOOP actually works) the attribute for whether logging is currently enabled or disabled will only pertain to the specific instance, or specific wire for the that object. Since this truly represents a single item, one log file, we need that attribute to be shared for all references to the instance of the log object. Since we allow this we can set an attribute on the log object in any task and it will be reflected in any other task that is using it. Think of the way a action engine or functional global works. However, in this case we provide discrete methods for the various actions.
I hope that made some sense. If not let me know since I just whipped up this response.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

"Hardcoding ini-File Settings" or "Automatic Revision Number with tortoise"

Hi all,
we use a SVN Repository with tortoise here at our company for version control.
I'd like to get the revision number hardcoded into the Application (.exe version).
I've allready found out, that there is some tool which can scan a directory and replaces a constant string in a file with the current revision number.
(So I could automatically generate a .ini file with "Ver=...RevNr" as content)
But I have no clue, how I can hardcode a file into the application with the labview builder.
(I think of something like the .ico file, which is hardcoded into the application too)
Has someone a sollution for this?
thanks
Mario Hirth
Solved!
Go to Solution.

Hi Mario,
I want to
ensure you mean what I think by "get a revision number hard coded in an Application"
When we build
an executable we
display a revision number on the front panel of our application and
we also have a Help -> About menu that displays the revision number
and other info like build
date and time.
If this is the sort of thing you want read on for some suggestions.
I have a software release VI
which contains control for things like build data, revision
number etc. This
Vi is shown from the help ->
about menu and
by an indicator on the
front panel of
our main application.
Manual revision control
Before every build
you edit this
Software Release VI
putting in the
details you want
in the controls, set these to be the default values and save the VI. When you build the new
values will then
be displayed in
your executable application.
This method is
simple to implement
and test; it is a good way to start. You just treat this VI as any other from the
point of view
of your source
control system.
However this method
has problems (people
forgetting to do
the change before
the build, people not knowing the next
number etc) and very
soon you will
want to move to an automatic revision control system.
I use and strongly
recommend the OpenG builder
rather than the
NI builder, for
a number of reason.
1) Good API,
to help you script you builds automatically
2) Good hooks
for pre-build, post-build
and call-backs VI
integration. For example
automatically zip up
your application after
a build an email to somebody.
3) A built
in revision system
you should be
able to get up and running without much trouble
4) The Build
configuration files are
in a human readable format.
In our system
which using ClearCase
and not SVN but the same principle applies, this
is a simplified
description.
I have three
basic files that
are used to auto revision, an ini file
that holds a record of all build for example - 001 29-Nov-2008, the software release
VI mentioned above
and I use the OpenG builder revision file to allow an easy built in hook in the OpenG builder.
When a build
starts a pre-build
trigger runs a
VI to look in the ini file to see what the next build number should
be, it then adds in a new entry with this new build number and various other information we
store, the .ini
file is then saved. In our ClearCase system I used a special config specification to
ensure that EVERYONE
sees the same
version of the
ini file (the
latest) and after
it is checked
in the latest
is immediately updated
with this new
save version again
so that EVERYBODY
can see it.
The pre-trigger VI then opens in edit mode the software release
VI in edit mode and plugs into the various control and indicator
the values read
out from the ini. The version of the software release VI is then saved and closed and then the build start. I do not worry about keeping
these edited versions
of the Software
Release VI in
the config control
system, in fact
I throw them away after the build is finished, they are in effect only templates
it is the ini file that
counts.
Hope this helps
as a simple guide
cheers
Dannyt
Danny Thomson CLAD
Sub10 Systems Ltd

We want your LabVIEW INI files!

Similar Messages

Maybe you are looking for