Leaderboard

Kudo up this idea: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Add-Variant-constant-to-the-Cluster-Class-amp-Variant-function/idi-p/1083987

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?

It might be better to use a notifier: This design will start and stop the inner loop with the same notifier (and destroying the notifier in the upper loop will shut down the lower loop when you want the program to stop). Using a User event is more complicated. -- James

I disagree - I think it would be easier for end users and OpenG developers if all packages are rolled out at once (like we did for v4.0).

Tell that to the people who flew the Mars Climate Orbiter INTO the planet, rather than into orbit, because one of their software packages was outputing in pound-seconds what the rest of the program thought was Newton-seconds. It's a Volt-Kelvin. Volt = Joules/Coulomb; Joule = kg m^2 s^-2; Coulomb = Amp-second --> Volt = kg m^2 s^-3 A^-1 The base unit is often unintelligible to humans, but as soon as you create an indicator and set it to "Watts", or do any math operation that requires consistent units (add, subtract, greater than, etc.) you'll get a broken wire and realize you multiplied the wrong things. And you'll get an error from your power module if you send it a VarMessage to set power at 1668.9 Volt-Kelvin. Basically, the computer is too dumb to tell you your unit is weird, but it's far better than you at identifying when the physical dimension is not the same between two quantities. Units can be some trouble, and internal to a module you might want to not use them, but for public communication between modules (possibly written at different times or by different programmers) they extend the bug-preventing value of type-checking to physical dimensions and eliminate the need to remember what units other modules expect things in. -- James BTW: the link to the prior conversation is actually here.

Not strictly just for fun; I use it as a way to sneak around mental blocks. When one side of my brain thinks the other side is only playing, it lets its guard down long enough for me to solve what's stumping me.

Thanks for your idea! I've found the answer in NI forum: Make a property node for the string indicator, set to write, and set the property to "Scroll Position". Then just wire a very large number to it or get the length of your string (string length under string pallete), and wire that in. http://forums.ni.com/ni/board/message?boar...uireLogin=False More detailed information could be found from the above link! Here is my steps: Right click the String Indicator, choose "Create" -> Property->Text->Scroll Position, and then create a numerial constant with a very large number and connect to the property node created just now. That's OK!

Yes thats it Thank you very much. Fantastic :thumbup: Need to check off this option in the builder options for it to work: Is it possible to automaticly register a filetype to an application when the application is installed?

Is this what you want?