Leaderboard

We're back again this year. Free 24 hours of virtual LabVIEW presentations. Come join us! https://www.glasummit.org/ We're also looking for presenters. I know some of you all have a lot of opinions...

2022 Q3 is still the large majority of our projects. Windows 11 support 64 bit RT, and things work fairly well. Yes like others have said some compile cache issues but very happy. We are migrating to 2025 Q1 as needed. I haven't used it as much as I have 2022 Q3, but it seems fairly good so far. I have seen a compile cache issue in 2025 Q1, and I have seen an RT related crash with XNet in development where the build was stable. So not all the confidence in the world but fine.

2020 was my favourite for a long time as we had issues on RT with many of the later versions. 2025 Q3 has been stable both on Win 11 and RT although the Linux RT Images are too bloated for some of the smaller sb/cRIO targets 😞. I did try to switch to 2026 when it came out, but ran into serious VISA issues on RT with it (which NI says has been fixed now). The next version we will move to is the upcoming 2026Q3 unless any issues show up during testing. It will include "native" SBOM-support which is good to have for the EU CRA requirements that kick in later this year (Still hoping for more significant feature updates soon though. The 40 year anniversary would have been a great time for some of those... 😮)

I've generally been recommending using at least 2025 because the project dependency list is no longer saved in the project file (it got recalculated at loading anyways), making GIT commits cleaner. And the in-place save for previous (introduced with 2024) is really nice to have. I have been using 2026Q1 for my development, including a major refactoring of my HAL architecture. I've had very few issues, almost all of which were fixed by clearing the object compile cache regularly (something I have a habit of doing anyways since at least 2016). And just to throw it out there, we are expecting 2026Q3 to drop any day now. No promises from NI on a date, but we are in Q3 now.

If I had to do it static at compile time my choice would be to have a Create xxx vi for every class that needs to be creatable. I don't like the class constant on the diagram at all.

If you have a specific structure for your chambers (ie everybody is under the "Hooovahh Chamber" directory), you could do a simple lookup and use the Get LV Class Default Value to dynamically load the classes. I do something similar with my HAL already, except I dictate what class to load based on a JSON file.

You should contact the developer. It may use features not available in earlier versions and it is a source control nightmare maintaining subtly difference versions.

该文件中有四行头文件 (4 rows of header in this file) 下面是一个程序，它将读取四个标题行，然后每次读取其余的 100 行 read csv per chunk of 100 rows.vi

New in LabVIEW 2020: C:\Program Files (x86)\National Instruments\LabVIEW 2020\vi.lib\picture\PNG\Draw Flattened Blended Pixmap.vi I didn't create this one. It is not in the palettes. I have asked that it be added in a future version.