Gribo

The thread setting and execution mode (re-entrant vs non re-entrant) are set in the VI properties, under execution. Re-entrant means that the OS (Or the LVRTE) can stop the VI's execution, switch to another thread, switch back, and the VI should continue as normal. Non-reentrant means the VI has to finish execution before such context switch happens, otherwise bad things (tm) happen.

You can copy the snippet. Explanation: The Bitmap is a constructor node, and you give it the image reference. Then you get the data, in this case, one RGB pixel at 0,0. If this works, the bitmap object has a method that returns the handle to the data. Edit: The Bitmap constructor is in System.drawing. If you are worried about tearing (capturing data from 2 different frames) you can use the PictureBox' VisibleChanged LoadCompleted callback.

Did you try this method?

Where does the ugly font and background noise come from? If you want to convert a .NET picture box to LV picture, you can construct a .NET Bitmap object with the image, and read its pixels.

I have validated this library against LibreOffice 7.2 and Windows 10.

Can you save it for an earlier version? Not everyone is on the latest and greatest. Also, The USB-6000 and precision timer do not make much sense. USB transfers don't have guaranteed microsecond timing with regard to the host's clock.

All FPGA based products have tough times now. Xilinx (AMD) and Altera(Intel) are the two major players and both have availability issues.

It's not just programmers, also other type of creative engineers.

There is also Adlink. I have some experience with their PXI cards, but not with their DAQs.

If you are open to non NI hardware, two kits come to mind, but good luck finding stock: Xilinx Kria and Nvidia Jetson.

Anecdotal evidence, I know, but here (Toronto, Canada) The number of open LabVIEW developer positions is practically 0.

I asked Omer to stop the spam, if it doesn't work, I know their manager

Re-use libraries whenever it is possible. I rather not reinvent the wheel. As for unused code, VI analyzer will find that. If a project has a Sub VI with no callers, I remove it from the project.

You know we like you, we decided to help you a bit.

That's not oil, that's battery acid.

There is a reason we call the NI forums the dark side.

Yes, it is probably the windows clipboard that does the string sanitizing. Strangely, from Notepadd++ to LV2020, I get a space instead of \00.

LV to notepad++ doesn't work -> Notpad++ uses C style strings for the paste from clipboard. LV to MS Word & Excel 365 doesn't work -> Same as above. It seems the LV to LV path allows null in the middle of a string, while the LV to Windows path doesn't.

Why do you have a null (\00) in the middle?

There was a page full of evil VIs that played tricks on the poor programmer trying to read them, I don't remember where I saw it.

LabVIEW enjoys security by obscurity right now. I am sure that the entire stack (Run time, Visa, DAQmx, whatever other services NI installs) have tons of holes and exploits.

I can amortize 20,000$ one time license costs, I can't amortize 500$/ month subscription. Python seems more attractive every day.

Inflation did not hit 10% yet.

Got to love how the 1 year subscription is 6K CAD and the 3 years is 24K CAD..

NI is shooting themselves in the foot with this approach. It is already difficult enough to find LabVIEW programmers. The IDE seems straight out of 2002, proprietary file formats, hard time integrating with version control and CI flows, Do they really want to drive away their potential customers? I use LV for many things, but I avoid the pay to deploy tools (IMAQ, Teststand). If I have to pay upkeep to NI, I'll recommend Python, the 3rd party hardware support is similar with pyVISA. No upkeep, no licenses, no deployment fees.