Home Community Idea Exchange LabWindows/CVI Ideas : New Ideas

LabWindows/CVI Idea Exchange

Community Browser
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Post an idea
1 Kudos
shel

Allow Large Arrays

Status: New Submitted by Member on 02-19-2012 11:02 PM 1 Comment

A byte array is limited to 2GB because the index is an int. Allow the use of long for an index so large arrays can be used.

Labels:
6 Kudos
Wolfgang

Provide clang updates on a (bi)annual schedule

Status: New Submitted by Trusted Enthusiast on 01-22-2012 07:19 AM Comment

It was a nice surprise when CVI provided clang as an external optimizing compiler. In the meantime, however, the initial clang version 1.0 has been significantly improved and now is at version 3.0 - but not for CVI users...

 

I would suggest that NI provides a current Windows binary of the compiler for everyone with a legal copy of CVI2010 or later. As the release cycles of CVI are quite long it would be convenient to obtain, on a biannual interval, interim updates of clang.

 

 

Spoiler

On a side note, this also would provide some motivation to keep/renew the SSP. Right now I consider it disappointing if the equivalent of several hundred Euros is a patch of CVI only. Other major companies such as Autodesk or Microsoft provide patches free of charge...

 

View All (1)
6 Kudos
Peter Cooper

CVI Applications running on the MAC OS, IPad, IPhone and Android Devices

Status: New Submitted by Member on 12-06-2011 05:58 PM Comment

Is NI road map going to allow applications that are developed with CVI for Windows to run also on the Apple MAC OS as well as run on IPhone and Android Devices? The current alternative to develop the applications for the Apple MAC OS is on X-Code IDE where the code with Objective C (and Objective C++). The code that is developed with CVI cannot be ported over to the MAC OS because Objective C is not based on the ANSI C Standard. X-Code IDE is a powerful but also a clumsy IDE and can be unforgiving. NI also provides the drivers for most its hardware for the MAC. In my opinion the CVI IDE has a much better IDE than X-Code and CVI is more intuitive to use from a development perspective.  Since there is open source CLang Compiler for the MAC why can't NI import the CLang Compiler to work with the MAC and IPhone? Both Windows and MAC use the same Intel Microprocessor. Intel also has a compiler for the MAC OS that is separate from the X-Code IDE.

To develop the applications for Android devices requires the Eclipse IDE. Can CVI be adapted to develop software with the Eclipse IDE like an add-on?

3 Kudos
CVI-User

How about a warning for things like "if (...) ;"?

Status: Under Consideration Submitted by Member on 11-11-2011 02:39 AM 2 Comment

I'd really appreciate a warning for "empty bodies" or whatever it is called, i.e. things like

 

for(...);
while(...);
if(...);

 If written like

if(...) { };

 it is OK.

 

Labels:
1 Kudos
Andre_Saller

Tile Sourcecode Windows inside the IDE

Status: New Submitted by Active Participant on 09-02-2011 05:27 AM 1 Comment

Tiling windows is only possible, when they are released from the IDE before. But navigating between the IDE and the released windows is difficult. It would be nice if the sourcecode and uir windows could be tiled INSIDE the IDE. Could look like this:

tiledwindow.JPG

Labels:
13 Kudos
MarcelK

Proper post mortem debugging support

Status: Under Consideration Submitted by Member on 05-25-2011 09:43 AM 2 Comment

The JIT debugger option in CVI 2010 is a nice step in the right direction, but only being able to debug builds that were compiled in "Debug" mode pretty much defeats the whole purpose of the idea. Debug builds are much too slow to be used in production and on my machines, if I ever use a Debug build, it probably already runs under the debugger anyway! Seeing that CVI is not even an optimizing compiler I cannot understand why release builds cannot be properly debugged. 

 

Thing is, the crashes in production are the important ones that I absolutely need to be able to investigate, and CVI does not provide ANY assistance in this area apart from being able to at least generate a MAP file. This is what I currently have to do: I have included code in my application that creates a memory dump and sends it to me when the application crashes or hangs. This dump I can then load into WinDbg and with a few tricks I can at least import the CVI MAP file to get some functions names in the stack traces, but that's it, all investigations have to be done on the assembly level. To quickly decipher stack frames, e.g. to have a look at local variables, I often even have to throw my OWN code into a disassembler (IDA Pro)! I'm really glad that this way I am now at least able to debug most crashes at all, even when they happen far away in a different country, but this aren't the 80s anymore and you can probably imagine that this process is hard and time consuming and very much annyoing. With code compiled in VC on the other hand I can load a MiniDump and have a look at the stack trace, variables and code on the source level without much hassles. 

 

Some ideas that could help:

 - Let me (JIT) debug release builds

 - Let me load MiniDumps into the debugger or

 - create PDB files that I can use together with a debugger that can load MiniDumps (WinDbg, VS)

 - Let me not only use an external compiler but also an external linker that generates PDB files for release builds (I don't like this solution as I use C99 features VC does not support, but I'm desperate here)

 

Okay, rant over for now, I think I really needed to vent a bit. Thanks for reading this far 😉 

 

All the best, Marcel 

0 Kudos
Miha_Vitorovic

Improve C preprocessor

Status: New Submitted by Member on 04-04-2011 04:20 AM 2 Comment

The C preprocessor in other compilers has seen some improvements over the years. Maybe you could freshen the CVI one up a little bit. With most modern C compilers there are some pretty advanced things that can be done in the preprocessor. But include those header files into a CVI project, and you start getting errors in the strangest places. And the cause of these isn't even some nasty trick, but pretty basic stuff for any other preprocessor.

Labels:
2 Kudos
tstanley

Implement the 'long double' type with 80 bits of precision.

Status: New Submitted by Active Participant on 01-10-2011 09:55 AM 2 Comment

Currently the 'long double' type has 64 bits of precision, which is the same as the 'double' type.  It would be handy on occasion to be able to use the full 80 bits of precision like is available with the Intel compiler.

Labels:
5 Kudos
Wolfgang

better documentation / support of external compilers and linkers

Status: Declined Submitted by Trusted Enthusiast on 11-26-2010 06:04 AM 7 Comment

In principle CVI supports external compilers for an optimized release version such as Intel's ICL and I managed to successfully compile release versions using ICL 11.1.

 

However, documentation on this issue is sparse.

 

It is even worse if one attempts to use an external linker which might be appropriate if one attempts to use e.g. Intel's MKL. Here I would love to see the support of external linkers in combination with an improved documentation.

 

Similarly, CUDA is becoming more attractive for more demanding floating point applications - I would consider it very useful if NI could provide e.g. an application note of how to do this in an easy to follow tutorial.

View All (2)
12 Kudos
Wolfgang

complete C99 support

Status: Under Consideration Submitted by Trusted Enthusiast on 10-29-2010 07:02 AM 9 Comment

well, the title says it all: extend the current partial support of C99 standard to full support

View All (2)
8 Kudos
Peter_Prinzen

configure batchbuilt; only compile certain projects...

Status: Under Consideration Submitted by Member on 10-13-2010 06:42 AM 3 Comment

Hi,

 

I would like to see an configuration of batchbuilt process. I have a big workspace with many projects; and would like to create different setups, like "compile only all server projects" or "compile all client projects". The workspace contains a big server-client -based software packages; some dll-projects used for server side only, some only client side.

 

Peter