From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
08-16-2021 07:17 AM
@Paul
Well my understanding was that at compile time the build array from constants and array constant are equivalent (in the runtime version),
and I've had problems with updating typedef enums when the constants are in arrays in the past - sometimes I've lost all of the values I had set when someone flicks it over between typedef and strict type def (I think is the use case), or it could be removing items.
The method I provided is one that doesn't mess up at edit time when dev changes are made, easily shows changes in SCC and seems to compile nicely - but then my enum arrays only tend to be less than 20 items long for state machines / commands (more than 4 is rare).
Rube is my specialty though😏
08-29-2021 12:23 PM - edited 08-29-2021 02:07 PM
While 1D arrays are sometime called "vectors", a 1D array with two elements is not a vector in the xy plane unless we define it like that and implement all the trigonometry when processing it as such.
Instead, we could just use a complex datatype that does everything under the hood correctly.
Compare:
09-20-2021 09:13 AM
Yes, that white box is my screen size (1366X768, minus window border en menu), shown in the navigation window...
What duplicate code? All the loops are different!
Glad it isn't my problem. My code lives in the class VIs in the top row, on the right.
09-20-2021 09:27 AM
You need a navigation pane for the navigation pane 😅
A map on the BD to let you know where you are.
09-20-2021 09:27 AM
wiebe@CARYA wrote:
Yes, that white box is my screen size (1366X768, minus window border en menu), shown in the navigation window...
What duplicate code? All the loops are different!
This might be acceptable programming in LabVIEW if it were targeting an FPGA. Well maybe not, since the FPGA has had various reference support for a while now and could even be cleaner there with subVIs.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-20-2021 09:36 AM
In there defense, I just found a newer version. By coincidence, there are no files in the project, except the old main...
It's 'better' (but far from good):
Man! If you're going to put so much work in refactoring, why not make it good?
09-20-2021 10:49 AM
09-20-2021 10:54 AM
@altenbach wrote:
If your navigation window looks like a CPU die, something is wrong 😄
See where?
09-20-2021 11:03 AM
09-21-2021 01:07 AM - edited 09-21-2021 01:08 AM
JÞB tells me my code is ripe for Rube-Goldberg
and simplified version by altenbach
EDIT:
Getting nominated for Rube-Goldberg must be akin to getting nominated for Golden Raspberry Award