X___

Interesting suggestion. Any idea how the multicore option works (Get/Set Number of Threads)? When I test this on a standalone VI, I get a number of 8 for "Transform" (which is what I am interested in testing) or "Linear Algebra" (I am using a 8 cores/16 threads laptop). When I include this as part of a larger project (launching a number of parallel tasks some of which use parallel loops), I end up with a "1" (in both tasks). I am not sure I should necessarily expect multithreading to be particularly useful in my case (rather small array sizes) but there isn't any explanation that I know of as to how this is supposed to work or be understood...

Actually that makes more sense: get an actually debuggable Python code and wrap it into a Python Node call. Un-commented spaghetti code is pretty much useless... The flat (single VI) LabVIEW generated code demo doesn't tell anything about the ability for this type of AI assistant to generate structured code. The first step is for NI to demonstrate that they can use AI to clean up (or expand/shrink) diagrams meaningfully. I believe the way they work is they are predicting each character on the fly I hope not... at least if they are using the thing right.

It's heavily scripted, but on face value, that looks promising.

BT What's wrong with the Picture control BTW? As long as you are not looking for super-fast updates (athough even that is not precluded), this is a very capable object...

Actually, here is the relevant info: Which VIs are Installed with NI-IMAQ and Vision Acquisition Software? and this: Is a License Needed to Work With NI Vision Acquisition Software? So it looks like nothing additional is needed for the computer on which the IMAQ hardware is installed (or from which it is run), but officially, any other computer (including a development computer) would. If your client is not using any IMAQ hardware, they are not supposed to use code (development or runtime) that uses these VIs. But again, I may have this all wrong, although that is what I remember from the time we were using an IMAQ frame grabber.

The latest NI License Manager release page: https://www.ni.com/en-us/support/documentation/release-notes/product.license-manager.html will clarify all that:

It doesn't say much of what the expected position reshuffling is going to be, but based on past history, it it unlikely they will not change anything to the management and strategy. I don't anticipate a reboot of LabVIEW or doubling down on investment and renewal of hopes for the tool though.

Here is an example that shows how that works: https://forums.ni.com/t5/LabVIEW/Can-I-read-16-bit-PNG-files-with-LabVIEW/m-p/4296823#M1255119

Yes

You would have to add a dummy graph that you would only show the legend of and fill that with half of your plot names (e.g. adding one empty plot for each pair). And of course hide the legend of your original graph. And respond to actions on the dummy graph to update your original graph.

There is NO public bug tracker in LabVIEW... In fact, I am not even sure there is beta program anymore...

A bit like Egyptian hieroglyphs.

For NI's defense, this is probably only visible on 1080p displays. It speaks volume about the state of LabVIEW when this becomes a new feature worth discussion on LAVA...

OK, my bad. I think I know what you are referring to: I am not sure what this means though, as I see no effect of the default font style on terminal, bundle, etc. sizes, only on the labels (in LV 2021 SP1).

Care to expand? Don't see anything in the changelog (sorry, there is no changelog).

https://seekingalpha.com/news/3949487-national-instruments-sale-process-likely-to-be-completed-in-early-april-report

I am looking forward to reading "Undo doesn't work anymore" in 2024Q3 and "colors are all gone" in 2027Q5... 🍿🍹

Almost got me. I was certain it was blue.

For info, this showed up in a VIM, in which I was playing back and forth between the representation of the input data to check different cases. I guess it throws off the IDE context help... and maybe more.

No comments and couldn't care less whether it is fixed or not.

https://www.fool.com/investing/2023/03/10/who-will-win-the-bidding-war-for-national-instrume/

https://finance.yahoo.com/news/ni-acquires-set-gmbh-accelerate-140000459.html

I am not the one confused by this post, but I have to wonder: with a 17 MB BD and a code complexity of 18.1, maybe considering breaking stuff into subVIs and refactoring is in order? In my case, this tool was helpful in setting priorities: https://www.abcdef.biz/pi_free.htm

I only meant that 2023 Q1 is the first version to officially support Windows 11 and that apparently, the head count in the LabVIEW R&D team is either classified or not to be admitted in public.

There is no need for gut feeling: the simple fact that they are not even trying to hype the future of LabVIEW is speaking volume. We implicitly learn that the LabVIEW team has been gutted or at least not given the means it needs to even keep in sync with OSes (https://www.ni.com/en-us/support/documentation/supplemental/22/ni-product-compatibility-for-microsoft-windows-11-.html). Heck, TestStand and VeriStand themselves, of which I know nothing but understand are where NI is investing its resources, are not Windows 11 ready. As for the rest, I guess you can check the release notes for 2023 Q1 (https://www.ni.com/pdf/manuals/labview-2023-q1-and-drivers.html#examples) to understand that the T's are not even crossed anymore, since the examples for this version are apparently to be found in the \LabVIEW 2022\examples directory... I am not sure it is fun to work at SpaceX, but I doubt there is much feeling of exhilaration at LabVIEW R&D nowadays...