LabWindows/CVI Idea Exchange

Post an idea

"tagfile" - ini file management

Here is the code of a kind of library "tagfile", I developed more than ten years ago, that I maintain and I always use for the management of my configuration *.ini files.

That works under Windows (CVI) or any UNIX system.

The code enables:

to read and write tags
to list the sections of an ini file
to list the tags of a section
to trap the errors

Most of others ideas about this issue on this blog are written under LabView ; I think a pure C code could be useful for some developers.

Comments are written in French but could be easily translated by any web AI API.

Below are example of functions for reading and writing a ini file. These functions are extracted from a program devoted to the dynamic excitation of a structure (mechanics).

Example of ini file

# --------------------------------------------
# DYNAMICS.INI
# Configuration "gros marteau"
# E.Ringot - BLUESPINE SAS - FRANCE
# https://www.blue-spine.com
# --------------------------------------------
[Sounds]
BUZZER = 0
SPEECH = 1
SPEECHSPEED = 1
SPEECHVOLUME = 93
#
# --------------------------------------------
[sampling]
# rate : Hz
# duration : s
PREFIX = BS
AUTOIMPACT = 6796480
RATE = 20000
DURATION = 10.000000
NBLOCKS = 32
#
# --------------------------------------------
[force]
# sensitivity : mV/N
# valmax : N
# excitation current : mA
DAQCHANNEL = cDAQ1Mod1/ai0
SENSITIVITY_0 = 0.233800
SENSITIVITY_1 = 0.233800
CURRENT = 20.000000
VALMAX = 21385.000000
#
# --------------------------------------------
[pretrigger]
# threshold : N
# hysfactor : no unit
THRESHOLD = 200.000000
HYSTFACTOR = 1.010000
REJECTION = 1000.000000
#
# --------------------------------------------
[acceleration]
# sensitivity : mV/g !!!
# valmax : m/s2
# excitation current : mA
DAQCHANNEL = cDAQ1Mod1/ai1
MODEL = PCB 35C33
SN = LW232997
SENSITIVITY = 101.000000
CURRENT = 10.000000
VALMAX = 480.000000
VALMA_x = 490.000000
#
# --------------------------------------------
[hammer]
# PCB Piezotronics impact hammer
MODEL = PCB 086D20
SN = 45451
TIP0 = GREY: Super soft
RANGE0 = 400
TIP1 = BROWN: Soft
RANGE1 = 450
TIP2 = RED: Medium
RANGE2 = 560
TIP3 = BLACK: Hard
RANGE3 = 1000
TIP4 =
RANGE4 = 0
TIP5 =
RANGE5 = 0
TIP6 =
RANGE6 = 0
TIP7 =
RANGE7 = 0
INDEX = 0
EXTENDER = 0
#
# --------------------------------------------
[post]
#
HMIN = 1.000000E-09
HMAX = 0.001000
HAUTO = 36180524
FLOW = 10.000000
FCUT = 100.000000
FAUTO = 36180524
# --------------------------------------------
FLOW = 10.000000
FCUT = 100.000000
[histo]
DIR0 = C:\dir0
DIR1 = C:\dir1
DIR4 = C:\Users\ringot\Documents\My Teaching\M1_DYNAMIQUE\tp\NI-CVI\polytp
DIR2 = C:\Users\ringot\Documents\My Teaching\M1_DYNAMIQUE\tp\NI-CVI\UT_Hammer
DIR3 = C:\Users\ringot\Documents\My Teaching\M1_DYNAMIQUE\tp\NI-CVI\UT_Newton
DIR5 = C:\Users\ringot\Documents\My Teaching\M1_DYNAMIQUE\tp\NI-CVI\UT_Newton
DIR6 = C:\Users\ringot\Documents\My Teaching\M1_DYNAMIQUE\tp\NI-CVI\UT_ForceOne
# --- EOF ---

Example of ini file reading

/* ---------------------------------------------------------------

LoadIni

Lecture du fichier inifile

--------------------------------------------------------------- */

int LoadIni(void)

{

#define cx cell.x

#define cy cell.y

Point cell;

int n, flag;

char *section;

long val;

section="sounds";

ReadShortTag(inifile,section,"BUZZER",(short*)&buzzer);

SetCtrlVal(tab4,TAB4_BUZZER,buzzer);

ReadShortTag(inifile,section,"SPEECH",(short*)&speech);

SetCtrlVal(tab4,TAB4_SPEECH,speech);

ReadShortTag(inifile,section,"VOICE",(short*)&voice);

SetCtrlVal(tab4,TAB4_VOICE,voice);

ReadLongTag(inifile,section,"SPEECHSPEED",&speech_speed);

SetCtrlVal(tab4,TAB4_SPEECHSPEED,speech_speed);

ReadLongTag(inifile,section,"SPEECHVOLUME",&speech_volume);

SetCtrlVal(tab4,TAB4_SPEECHVOLUME,speech_volume);

section="sampling";

TagErrChk(ReadLongTag(inifile,section,"RATE",&val));

SetCtrlVal(tab0,TAB0_RATE,rate=val);

TagErrChk(ReadDoubleTag(inifile,section,"DURATION",&duration));

SetCtrlVal(tab0,TAB0_DURATION,duration);

TagErrChk(ReadLongTag(inifile,section,"NBLOCKS",&nblocks));

SetCtrlVal(tab0,TAB0_NBLOCKS,nblocks);

TagErrChk(ReadIntTag(inifile,section,"AUTOIMPACT",&autoimpact));

SetCtrlVal(tab0,TAB0_AUTOIMPACT,autoimpact);

TagErrChk(ReadStringTag(inifile,section,"PREFIX",prefix));

if (!*prefix) strcpy(prefix,"CORROHM");

SetCtrlVal(tab0,TAB0_PREFIX,prefix);

section="force";

TagErrChk(ReadStringTag(inifile,section,"DAQCHANNEL",forceChannel));

SetCtrlVal(tab1,TAB1_DAQCHANNEL,forceChannel);

TagErrChk(ReadDoubleTag(inifile,section,"SENSITIVITY_0",forceSensitivityList));

SetCtrlVal(tab1,TAB1_SENSITIVITY_0,forceSensitivityList[0]);

TagErrChk(ReadDoubleTag(inifile,section,"SENSITIVITY_1",forceSensitivityList+1));

SetCtrlVal(tab1,TAB1_SENSITIVITY_1,forceSensitivityList[1]);

TagErrChk(ReadDoubleTag(inifile,section,"CURRENT",&forceExcitationCurrent));

SetCtrlVal(tab1,TAB1_CURRENT,forceExcitationCurrent);

TagErrChk(ReadDoubleTag(inifile,section,"VALMAX",&forceMax));

SetCtrlVal(tab1,TAB1_VALMAX,forceMax);

section="pretrigger";

TagErrChk(ReadDoubleTag(inifile,section,"REJECTION",&rejection));

SetCtrlVal(tab1,TAB1_REJECTION,rejection);

TagErrChk(ReadDoubleTag(inifile,section,"THRESHOLD",&threshold));

SetCtrlVal(tab1,TAB1_THRESHOLD,threshold);

TagErrChk(ReadDoubleTag(inifile,section,"HYSTFACTOR",&hystfactor));

SetCtrlVal(tab1,TAB1_HYSTFACTOR,hystfactor);

section="acceleration";

TagErrChk(ReadStringTag(inifile,section,"DAQCHANNEL",accelChannel));

SetCtrlVal(tab2,TAB2_DAQCHANNEL,accelChannel);

TagErrChk(ReadDoubleTag(inifile,section,"SENSITIVITY",&accelSensitivity));

SetCtrlVal(tab2,TAB2_SENSITIVITY,accelSensitivity);

TagErrChk(ReadDoubleTag(inifile,section,"CURRENT",&accelExcitationCurrent));

SetCtrlVal(tab2,TAB2_CURRENT,accelExcitationCurrent);

TagErrChk(ReadDoubleTag(inifile,section,"VALMAX",&accelMax));

SetCtrlVal(tab2,TAB2_VALMAX,accelMax);

TagErrChk(ReadStringTag(inifile,section,"MODEL",amodel));

SetCtrlVal(tab2,TAB2_MODEL,amodel);

TagErrChk(ReadStringTag(inifile,section,"SN",aSN));

SetCtrlVal(tab2,TAB2_SN,aSN);

AllocateMemory();

section="hammer";

TagErrChk(ReadStringTag(inifile,section,"MODEL",fmodel));

SetCtrlVal(tab1,TAB1_MODEL,fmodel);

TagErrChk(ReadStringTag(inifile,section,"SN",fSN));

SetCtrlVal(tab1,TAB1_SN,fSN);

// tips

GetNumListItems(hammerHandle, HAMMER_TIPLIST, &n);

DeleteListItem (hammerHandle, HAMMER_TIPLIST, 0, n);

GetNumTableRows (tab3, TAB3_TABLE, &n);

DeleteTableRows (tab3, TAB3_TABLE, 1, n);

cy = 1; n = 0;

do {

char var[8], label[64];

int ftip;

sprintf(var,"TIP%d",n);

if (ReadStringTag(inifile,section,var,label)) break;

if (!*label) break;

sprintf(var,"RANGE%d",n);

if (ReadLongTag(inifile,section,var,&ftip)) break;

if (!ftip) break;

InsertListItem(hammerHandle, HAMMER_TIPLIST,-1,label,ftip);

InsertTableRows (tab3, TAB3_TABLE,-1, 1, VAL_USE_MASTER_CELL_TYPE);

cx=COL_TIP; SetTableCellVal(tab3,TAB3_TABLE,cell,label);

cx=COL_FRQ; SetTableCellVal(tab3,TAB3_TABLE,cell,ftip);

cy++; n++;

} while(1);

SetCtrlVal(tab3,TAB3_NTIPS,n);

if (ReadLongTag(inifile,section,"INDEX",&n)) n=0;

SetCtrlIndex(hammerHandle,HAMMER_TIPLIST,n);

cx=COL_SEL; cy=n+1;

SetTableCellVal(tab3,TAB3_TABLE,cell,"X");

TagErrChk(ReadLongTag(inifile,section,"EXTENDER",&flag));

SetCtrlVal(hammerHandle,HAMMER_RADIOEXTENDER,flag);

forceSensitivity=forceSensitivityList[flag];

// dir history

TagErrChk(ReadHistoDir(inifile));

tagstop:

return tagerr;

#undef cx

#undef cy

} // LoadIni

Example of ini file writing

/* ---------------------------------------------------------------

SaveIni

Sauvegarde du fichier inifile

--------------------------------------------------------------- */

int SaveIni(void)

{

#define cx cell.x

#define cy cell.y

Point cell;

int tipindex=0, n;

char *section;

// -- TAB4

section="Sounds";

GetCtrlVal(tab4,TAB4_BUZZER,&n);

WriteShortTag(inifile,section,"BUZZER",buzzer=(short)n);

GetCtrlVal(tab4,TAB4_SPEECH,&n);

WriteShortTag(inifile,section,"SPEECH",speech=(short)n);

GetCtrlVal(tab4,TAB4_SPEECHSPEED,&speech_speed);

WriteLongTag(inifile,section,"SPEECHSPEED",speech_speed);

GetCtrlVal(tab4,TAB4_SPEECHVOLUME,&speech_volume);

WriteLongTag(inifile,section,"SPEECHVOLUME",speech_volume);

// -- TAB0

section="sampling";

GetCtrlVal(tab0,TAB0_RATE,&rate);

TagErrChk(WriteLongTag(inifile,section,"RATE",rate));

GetCtrlVal(tab0,TAB0_DURATION,&duration);

TagErrChk(WriteDoubleTag(inifile,section,"DURATION",duration));

GetCtrlVal(tab0,TAB0_NBLOCKS,&nblocks);

TagErrChk(WriteLongTag(inifile,section,"NBLOCKS",nblocks));

GetCtrlVal(tab0,TAB0_AUTOIMPACT,&autoimpact);

TagErrChk(WriteIntTag(inifile,section,"AUTOIMPACT",autoimpact));

GetCtrlVal(tab0,TAB0_PREFIX,prefix);

TagErrChk(WriteStringTag(inifile,section,"PREFIX",StrClean(prefix)));

// -- TAB1

section="force";

GetCtrlVal(tab1,TAB1_DAQCHANNEL,forceChannel);

TagErrChk(WriteStringTag(inifile,section,"DAQCHANNEL",forceChannel));

GetCtrlVal(tab1,TAB1_SENSITIVITY_0,forceSensitivityList);

TagErrChk(WriteDoubleTag(inifile,section,"SENSITIVITY_0",forceSensitivityList[0]));

GetCtrlVal(tab1,TAB1_SENSITIVITY_1,forceSensitivityList+1);

TagErrChk(WriteDoubleTag(inifile,section,"SENSITIVITY_1",forceSensitivityList[1]));

GetCtrlVal(tab1,TAB1_CURRENT,&forceExcitationCurrent);

TagErrChk(WriteDoubleTag(inifile,section,"CURRENT",forceExcitationCurrent));

GetCtrlVal(tab1,TAB1_VALMAX,&forceMax);

TagErrChk(WriteDoubleTag(inifile,section,"VALMAX",forceMax));

section="pretrigger";

GetCtrlVal(tab1,TAB1_REJECTION,&rejection);

TagErrChk(WriteDoubleTag(inifile,section,"REJECTION",rejection));

GetCtrlVal(tab1,TAB1_THRESHOLD,&threshold);

TagErrChk(WriteDoubleTag(inifile,section,"THRESHOLD",threshold));

GetCtrlVal(tab1,TAB1_HYSTFACTOR,&hystfactor);

TagErrChk(WriteDoubleTag(inifile,section,"HYSTFACTOR",hystfactor));

// -- TAB2

section="acceleration";

GetCtrlVal(tab2, TAB2_MODEL,fmodel);

TagErrChk(WriteStringTag(inifile,section,"MODEL",amodel));

GetCtrlVal(tab2, TAB2_SN,fSN);

TagErrChk(WriteStringTag(inifile,section,"SN",aSN));

GetCtrlVal(tab2,TAB2_DAQCHANNEL,accelChannel);

TagErrChk(WriteStringTag(inifile,section,"DAQCHANNEL",accelChannel));

GetCtrlVal(tab2,TAB2_SENSITIVITY,&accelSensitivity);

TagErrChk(WriteDoubleTag(inifile,section,"SENSITIVITY",accelSensitivity));

GetCtrlVal(tab2,TAB2_CURRENT,&accelExcitationCurrent);

TagErrChk(WriteDoubleTag(inifile,section,"CURRENT",accelExcitationCurrent));

GetCtrlVal(tab2,TAB2_VALMAX,&accelMax);

TagErrChk(WriteDoubleTag(inifile,section,"VALMAX",accelMax));

// -- TAB3

section="hammer";

GetCtrlVal(tab1, TAB1_MODEL,fmodel);

TagErrChk(WriteStringTag(inifile,section,"MODEL",fmodel));

GetCtrlVal(tab1, TAB1_SN,fSN);

TagErrChk(WriteStringTag(inifile,section,"SN",fSN));

// tips

GetNumListItems(hammerHandle, HAMMER_TIPLIST, &n);

DeleteListItem (hammerHandle, HAMMER_TIPLIST, 0, n);

GetNumTableRows (tab3, TAB3_TABLE, &n);

for (cy=1; cy<=MAX_NBTIPS; cy++)

{

char var1[8], var2[16], label[64];

int k=cy-1, ftip;

sprintf(var1,"TIP%d",k);

sprintf(var2,"RANGE%d",k);

if (cy<=n)

{

cx=COL_SEL; GetTableCellVal(tab3,TAB3_TABLE,cell,label);

if (*label=='X') tipindex=cy-1;

cx=COL_TIP; GetTableCellVal(tab3,TAB3_TABLE,cell,label);

cx=COL_FRQ; GetTableCellVal(tab3,TAB3_TABLE,cell,&ftip);

InsertListItem(hammerHandle,HAMMER_TIPLIST,-1,label,ftip);

}

else

{

*label=0; ftip=0;

}

TagErrChk(WriteStringTag(inifile,section,var1,label));

TagErrChk(WriteLongTag(inifile,section,var2,ftip));

}

SetCtrlIndex(hammerHandle,HAMMER_TIPLIST,tipindex);

TagErrChk(WriteLongTag(inifile,section,"INDEX",tipindex));

AllocateMemory();

TagErrChk(WriteHistoDir(inifile));

tagstop:

return tagerr;

#undef cx

#undef cy

} // SaveIni

Download All

.editorconfig support

CVI provides the ability to use syntax coloring (which is nice )

Right now, C keywords share one color - these keywords include the data types int, double, ...

Unfortunately, the boolean types (bool defined by stdbool.h), including the macros true and false, and the size and pointer difference types are not included, e.g. size_t, intptr_t, ...

This is not a problem because CVI also allows adding user-defined tokens for coloring, it even provides the option to add the VISA types.

In that sense we have the possibility to have core and extra types marked in two different colors - which is also nice.

Now I'd like to mark (my) constants as well, in a different color, and this is not possible.

My suggestion thus is to add a second group of user tokens, which can be colored differently.

Thanks

Make cvi.exe a 64 bit application

It appears that cvi.exe can run into serious memory problems for larger projects due to a memory-hungry generation of source code browse information.

The solutions suggested (* don't generate browse information for larger projects or * don't use larger projects) are not too helpful. In my opinion, a much better solution would be to provide cvi.exe as a 64 bit application.

Because a crashing CVI is a serious limitation I hope this wish will make it soon.

Thanks...

View All (1)

LabWindows/CVI lags behind the more recent developments in its programming language, C. At present, it only partially supports the C99 standard, not to mention the improved Unicode support of the current standard, C11.

Since odds are that Unicode finally will be supported in a future version of LabWindows/CVI, this might be a good opportunity to also ask for support of the current standard of CVI's programming language, C11, allowing the use of UTF encoded strings and also including updated libraries (e.g., supporting complex or long long) and debugging tools (data tooltips and variable view supporting complex numbers, for example). It also would help to improve C/C++ compatibility for programs that use complex floating-point values.

I really would appreciate it if the LabWindows/CVI project will show some strong signs of development and accompany us for the next 30 years, too.

View All (1)

On high resolution monitors, the icons in the toolbar, project tree, and library tree in CVI are really tiny. Font sizes can be configured, but icon sizes cannot.

As usage of high resolution monitors becomes more common, I think it would be very helpful to provide some configuration options to optimize the appearance and usage of the CVI environment on monitors of varying resolution. Please refer to the attached screenshot for an example of this behavior.

View All (2)

At present, when you double-click on a .cws or .prj file the most recent version of the CVI IDE is launched with the selected .prj or .cws file loaded.

However, both project and workspace files include the release of CVI they are developed on, so it would be possible to search in the system whether that release is installed and open it instead of the most recent one. This is crucial when you need to modify a program already deployed to a customer but do not want / is not possible to update the target machine configuration installing a newer Run-Time module than the one already installed.

At present you have no control over this event, but consider also that in case you make modifications to the UIR files also, it may become difficult to revert to the original IDE format; for this reason when I need to update an old program I need firstly to open the project file in notepad to see which CVI release to use for this.

If automating the launch in the correct release is not possible, at least issue a warning stating the difference in the IDE release used with respect to the original one.

Most user settings are kept in either the project or the workspace file. Unfortunately, this is not true for building a function tree (Options/Generate Function Tree). Starting CVI the previous entries are lost. Actually this is an old issue but may be not too old to be improved...

So I suggest to save the information about Instrument name, Function prefix, Default qualifier, and Output function tree in the appropriate configuration file (prj or cws)

Thanks

Hello,

I have a very elaborate Front Panel, developed in LabVIEW 8.6, which I'd like to import into my LabWindows/CVI 2013 development environment.

The background is that the new company colleagues are very proficient in C and want to use LabWindows/CVI to re-program the current state of the software and maintain and update only using LabWindows/CVI in the future.

This would be very usefull, since it would save a lot of time and keep the naming of the elements in the front panel as-is. For the customers it would mean, having the same tool they are used to work with and receive much faster and better service when it comes to changes or additional functionality.

If there is already a way to do this I'd be happy to have a step by step guide.

According to the feedback from the forum, this still doesn't exist. (http://forums.ni.com/t5/LabWindows-CVI/Can-I-convert-a-LabVIEW-Front-Panel-into-a-LabWindows-CVI-User/td-p/3044003)

In CVI 2013 is option “Run -> Attach to Process…” and new is option “<< Running >> -> Detach from a process” during debugging, which is very good to debug TestStand sequence and CVI DLL, advantageous if I need to update CVI code and do not have to launch TestStand again and again after new CVI code is builded. Hovewer, to attach CVI DLL to a process is always necessary to do next steps: Run -> Attach to Process…, then select process from a list (seqedit.exe) and click OK. I would appreciate similar option as “Specify Executable to Debug…” or key shortcut to attach process directly to TestStand in one click or using simple key shortcut.

Déphasage d'un signal carré

Initialization of the PCI6220 card

As discussed here and here, CVI does not re-open workspace files in the order they were when CVI was closed; I am referring to confined workspace, not freely floating windows.

As a result, starting CVI one first has to locate all the files, where did the include file go...? If you happen to have some more tabs this is a waste of time.

Also, as Roberto mentioned, you can not easily use the short cut keys Ctrl-1 etc. because of the changing assignment.

So, in short, I am asking to improve this behavior and maintain the tab order of CVI workspace files, that is, re-arrange/re-open the tabs in the order they were when CVI was closed.

Thanks!

View All (2)

Allow renaming a file within the project

While it is possible to add, remove and replace files in a CVI project it is not possible to rename or duplicate a file.

This is useful for example if a large source code file shall be split to speed up compilation. Although this file operation could be done outside of CVI associated tags would be lost.

A workaround has been offered here but a more elegant and simple solution would be welcome. Hence I suggest to provide two more commands to add and duplicate a file including its associated tags and breakpoints...

Thanks.

View All (2)

The option tooltip is very good feature what is the problem is it is only for the controls. If I want to show tooltip for listbox then it is fine but what if someone wants to show tooltip for active rows. It simply doesn't.

This is very basic but one of the disadvantage of labview over .NET.

This needs to be fixed

Hello,

usually I work on my projects on two different computers (home/work or development/lab). I would like to see a possibility to more easily move my project back and forth, say by providing two new menu commands

File / Import Project and File / Export Project

I imagine that the Export command generates a zip file consisting of all files required to build the executable (and a distribution) and also exports the editor preferences (probably without the window positions because different computers may have different screen resolutions) etc. The Import command then should load the *c., .cds, .cws, *.fp, *.h, *.prj and *.uir files, import the editor settings, adjust the library menu and load any instruments.

Thanks!

View All (1)

Save debug information

View All (2)

function list

I would like to suggest a function tree view in CVI. I feel this is sorely missing. Many times, I want to jump right to a function, but I don't remember where it is. In a single C file with 1,000+ lines, this can be very aggravating.

For this reason, I tend to use Notepad++ for the heavy lifting, along with the Source Cookifier plugin. See attached screenshot of that plugin.

There are options in the plugin to enable certain features, such as the global and local variables in addition to the function names. When you are inside a function in the souce editor, the tree updates with a selection to show that you are inside that function. This is very helpful with functions that have more lines than available veritcal screen space. This way, I don't have to scroll up to see what function I'm looking at. I simply look at the tree with a glance and I know.

What is the point of this Idea Exchange, when there is such a low uptake rate from NI?

There have been many very good suggestions posted here, but only 6 are labelled as "In Beta", which I assume means will be in the CVI release this autumn. There are 106 "Under Consideration", but there is no indication what is required to move them to "In Beta". For instance, Wolfgang posted "Reduce and document the NI services running after Windows logon" on ‎04-01-2011. It went to "Under Consideration" on 08-15-2011. Two Years from the original posting, we still have nothing!

How do I justify renewing our Volume Licence Agreement when the LabWindows development effort within NI is so small?

How many people actually are on the full time LabWindows team within NI?

Starting from CVI2010, the User Interface Browser and the Attribute Browser are both located on the right of the UIR editor in the Workspace window.

I'd like to be able to hide these windows when required: when working on small screens like when you use a laptop these windows occupy a lot of space even if you reduce their size at the minimum.

In addition, the ability to choose which window to display on the bottom left could be a good option: up to version 2009 the bottom left side of the workspace window switched between the library tree (source editor) and the attribute browser (UIR editor).

Ideally, while in the UIR editor I would like to be able to:

Choose whether to show some window on the right side or not
In case nothing is shown on the right, choose whether to have the attribute browser, the library tree or the user interface browser in the bottom left angle

View All (2)

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

LabWindows/CVI Idea Exchange

"tagfile" - ini file management

.editorconfig support

add a second group of user tokens for syntax coloring

Make cvi.exe a 64 bit application

Support the current standard for the C programming language, C11

Conifgurable Icon Sizes in the CVI Development Environment

Automate opening an existing project in the proper release of CVI

Remember values for generating a function tree

Can I convert a LabVIEW Front Panel into a LabWindows / CVI User Interface File ?

Small improvement to automate debugging option in CVI 2013

Déphasage d'un signal carré

Initialization of the PCI6220 card

Please maintain the tab order of CVI workspace files

Allow renaming a file within the project

Tooltips for active rows in listbox

Portable 'Projects' (Import/Export 'Project')

Save debug information

function list

Actually implement some of these ideas; only 6 ideas are in Beta compared to 271 New or Under Consideration

Ability to hide the User Interface and Attribute browser boxes