Saverio

Just to clarify: my question about whether the operation is a bug or feature had to do with the "uniterated" loops not passing references through, and not about the array. The example I posted about the array was in response to Samapico's question about how to get a 0x2 array, which was a reference to Ben's comment having to do with other iteration behaviors with loops.

Like this: Are we considering this behavior a bug, or by design? Greg seems to indicate it's by design, but Aristos is implying it's a bug.

Obviously, but as I pointed out, it was not clear the level of preciseness the OP wanted, and it was unclear (until just recently) whether the OP was trying to measure a basis timing (i.e., how well does this design work in principle), vs. the difference in timing over a large quantity of computers.

It really shouldn't matter that much. LabVIEW code is compiled regardless of whether you're in the development environment or the run-time environment. Are you trying to determine differences between different machines?

Ravi, FYI: your VI always returns a count that is one less than the actual number of lines.

If all you're interested in is running time of VIs then the built-in performance metrics should suffice. Go to Tools -> Profile -> Performance and Memory. This should give you a reasonable estimate to start with. If it appears that you need something more precise, then you can at least determine what it is that you need.

Are you looking for this: http://zone.ni.com/r...epts/checklist/ ? Here's another one: http://zone.ni.com/d.../p/id/5560#toc1 And this: http://www.amazon.com/LabVIEW-Style-Book-Peter-Blume/dp/0131458353

If I had a quarter for every little subtlety like this that I've missed over the years then I wouldn't have to worry about my retirement anymore.

You posted the question on the NI forums yesterday. Please be aware that those are public forums, and the volume of posts there is extremely high. Thus, it is easy for threads to be lost. I am extremely active on the NI forums and I did not even see your thread. This does not mean it got ignored. It simply got lost in the cacophony. As for your question: you will not even have a hope of doing this without the source code to the lsb. The .lsb files are compiled code, and it's a binary file with a specific format. You would need to go through a lot of steps in order to get to at least assembly language. To get it to C you'd need to do this yourself. However, the disassembly of the CIN code may even be illegal. You said you don't know which .lsb file goes with which CIN node. Can you guess?

Not sure what to say... I ran the executable and it ran just fine. As asked have you tried this on another PC?

See here: http://forums.ni.com/t5/LabVIEW/How-to-highlight-a-cell-in-a-table/m-p/755700/highlight/true#M346131

If you expand the Dependencies node for the project what do you see? Do you see something like this: If not, try refreshing the Dependencies (right-click on the tree node). How is your build spec set up? Which edition of LabVIEW are you using? I don't mean the version, I mean Full, Professional, etc. Did you install any other software that would have affected the LV2010 Run-Time Engine? This may be a problem with the Run-Time Engine. Perhaps a repair of the installation would fix it? Do you have the correct Run-Time version installed (the standard, and not the minimum version)?

The kernel32 DLL that ships on a 64-bit Windows OS is 64-bit, even though the name has name of the DLL has "32" at the end. The "32" is misleading in this case. MS kept the name the same so as not to break all the apps that people had written that directly linked to it.

Highlight in what manner? Change the background? Put a highlight border around it? LabVIEW already puts in a little text box when you click on a cell, to indicate where you're typing. What did you need beyond this?

Have you tried using the Windows API? The function GetProcessMemoryInfo is a likely candidate. I would caution, you however, to better define which memory you are talking about. I'd recommend reading this thread: http://stackoverflow.com/questions/63166/how-to-determine-cpu-and-memory-consumption-from-inside-a-process

You initially started off indicating that you suspected the Mean VI. Why? What led you to believe that was the culprit, especially since the error message doesn't really tell you anything. If you remove it from your code does the executable work?

The "row", "column", and "page" are just terms to aid us poor humans. A 2D array can be viewed as a table, so you can refer to the horizontal thingies are "rows" and the vertical thingies as "columns". With a 3D array you can think of it as having multiple tables stacked on top of each other, and you can consider each of these "sheets" as "pages". They're really just terms to aid in "human-speak". For instance, what do you refer to the 4th index for a 4D array? Chapter? Book? Or, for the physicists out there, time?

I haven't tried this with 8.0, but I know to get 8.2 installed on Windows 7 you need to run the installer as administrator, regardless of what OS you select for compatibility. Even if you're logged in as a user with admin rights you have to right-click the setup.exe file and select "Run as administrator" (or check the box at the bottom of the compatibility dialog as shown in the picture above). The same may be true for 8.0, but like I said, I have not tried it with 8.0. I also have 8.0 installed with Windows XP Mode.

Ouija board? Magic Eight Ball? Carnak the Magnificent? In all seriousness, if you want a serious response you will need to provide a better question. Interface how? Interface to do what? What have you researched? What have you tried? Have you tried the input VIs in LabVIEW?

I've always used a global variable for this sort of thing. If it's something that has an astronomically small chance to change I just set the default value of the control and save it. Chances are that if the value needs to change, then something else in the software needs to change anyway. You may wish to consider voting for this idea: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Adding-CONSTs-to-LabVIEW/idi-p/942213

For those responding: this was also posted on the NI site here: http://forums.ni.com/t5/LabVIEW/is-it-possible-in-Labview-Suggest-me/td-p/1686440 If responding you may wish to review what has already been said there so as not to repeat suggestions.

What does your code do? Calling any external code, like DLLs or ActiveX or .NET? One of those may be crashing it. While you may not be able to post the code you can at least provide us with a better idea of what your code is actually doing...

OK, that makes sense. In that case, attached is a simple example that replicates the last example on that page. MessageBox Example.vi

I'm sorry, but your question is not clear. Are you referring to using the Call Library Function Node? And what "windows message box's [sIC]" are you referring to? Are you asking how to use the Call Library Function Node? If so, there is an extensive example that ships with LabVIEW (Help -> Find Examples). Just search for "DLL". Please provide a better explanation of what you are trying to do.

Don't get me wrong - I completely agree with you. I was actually responding more to Neil's comment about it still being "broken" in 2011. I was just pointing out that technically it's not broken (at least in my opinion). I agree that you can make an argument here that although you have 2 different classes, you're fundamentally dealing with references, so perhaps the Cluster to Array could be made to take that into account. Either way, the Idea Exchange is a good place to post this as well as here. (I did kudo your idea. )