LabWindows/CVI Idea Exchange

Post an idea

Would it be possible to allow ".." to be used as a "Custom Copy Directory" in the "Target Settings" dialog box (for dynamic link library projects)? Or in other words, I would like the ability to specify that the Custom Copy Directory should always be one up from the project directory. That way this functionalty won't break when I rename the directory or move the project between computers where the complete path is not the same. A similar thing would also be handy in the "Specify Executable to Debug" dialog box. Thanks.

I had a customer associated with SR# 7325346 ask how to change the maximum value for his Y axis in CVI. I rightfully directed him to the SetAxisScalingMode function. The customer told me that they were using an equation to determine the Max parameter for their Y axis [YMax=2*x + sqrt(x) + log(x)] or something to that effect. He also said that the equation could change to something else, and he would like to change the equation on the fly within CVI.

Basically, he's asking for functionality that would enable a text box to act similar to an Excel cell, which could evaluate simple equations such as add(val1,val2) or sqrt(val3). We should build a tool that makes this possible.

View All (4)

Running an application in maximized mode (with main window covering the task bar), if you switch to the desktop (i.e. pressing Windows key+D), you are no longer able to return back to your application. You will see your application button in the task bar, but nothing happens clicking on it, nor you successed using Task Manager, you have simply lost your application.

Imagine you need to use a program in maximized mode and the program controls production tools and machineries, involving money and safety issues, it is an embarrassing situation.

I hope you can fix it soon, today I've fixed it training the operators to avoid the hanging sequence.

Thank you.

Sergio

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

View All (4)

LabWindows/CVI Idea Exchange

"Custom Copy Directory" improvement idea

Excel code evaluation within CVI input

Losing control of applications running in maximized mode!

Proper post mortem debugging support

panel events: MINIMIZE and RESTORE