11-10-2022 10:04 AM
@Yamaeda wrote:
@altenbach wrote:
Anyone care to explain the possible thought process leading to all that?
Arrays should be handled by references. All code is better with references. I've learned that in that C++ course i took in -95.
I am sure you did not learn to create a new reference and then destroy it once per iteration in a tight loop.
11-11-2022 08:32 AM
@altenbach wrote:
@Yamaeda wrote:
@altenbach wrote:
Anyone care to explain the possible thought process leading to all that?
Arrays should be handled by references. All code is better with references. I've learned that in that C++ course i took in -95.
I am sure you did not learn to create a new reference and then destroy it once per iteration in a tight loop.
My head is still stuck at the 2 DVRs that operate "inplace" and wire the values straight through. (Gain[] and Offset[])
Did you ask the OP? What results could a phrenologist observe?
11-12-2022 02:44 AM
11-18-2022 09:49 AM
@JÞB wrote:
@altenbach wrote:
@Yamaeda wrote:
@altenbach wrote:
Anyone care to explain the possible thought process leading to all that?
Arrays should be handled by references. All code is better with references. I've learned that in that C++ course i took in -95.
I am sure you did not learn to create a new reference and then destroy it once per iteration in a tight loop.
My head is still stuck at the 2 DVRs that operate "inplace" and wire the values straight through. (Gain[] and Offset[])
Did you ask the OP? What results could a phrenologist observe?
They are simply needed to access the data for the calculation. Much like an &ref in C++.
11-21-2022 08:55 AM - edited 11-21-2022 08:59 AM
There are many ways to quarter a 64bit integer, some are simpler than others. (seen here).
(And yes, SGL would be plenty to do a floating point representation of a 16bit integer, but the decimation operation requires DBL later)
11-21-2022 11:34 AM
@altenbach wrote:
There are many ways to quarter a 64bit integer, some are simpler than others. (seen here).
(And yes, SGL would be plenty to do a floating point representation of a 16bit integer, but the decimation operation requires DBL later)
I'll take a guess at your question: "Why so convoluted?".
Many people have no interest in learning anything new. When they need to code something, they won't even bother searching the palettes for something that might work well. Instead they just start hacking away with whatever limited knowledge is in their heads.
12-01-2022 09:51 AM - edited 12-01-2022 11:18 AM
Maybe you need code that takes 2 DBLs and inflates it to 100k (or more?) DBLs with more hot air than the Albuquerque balloon fiesta.
Here's what to do (seen here ) 😄
12-14-2022 07:54 AM
The accepted solution equivalent of cutting your finger off to prevent a mouse button press.
12-14-2022 11:16 AM
@AeroSoul wrote:
The accepted solution equivalent of cutting your finger off to prevent a mouse button press.
So, how would you solve it?
12-14-2022 01:59 PM
wiebe@CARYA wrote:
@AeroSoul wrote:
The accepted solution equivalent of cutting your finger off to prevent a mouse button press.
So, how would you solve it?
I would also like to know. Using an Abort button to Stop a vi is extremely dangerous. It is precisely why no deployed apps have an abort button (unless a LabVIEW Developer forgets to rip it off)
I commonly remove the Abort button. Removing the button also disables "CTRL+." or any hotkey otherwise assigned to Abort VI. I started doing that shortly after joining these forums because of advice received from reading many threads. If you have other practices I would be happy to hear your thoughts.