Neil Pate

Sorry I did not really offer any suggestions, I am not sure how to flush an ini file (never needed to). I normally close the file immediatley after modifying the contents.

I am a litle surprised LabVIEW lets you wire this together, as the reference coming out of the Open Config Data is not actually a file reference it is a queue reference. So when you try and Flush you are passing in a Queue reference not a normal File reference, so this will not work.

A few years ago I have managed to get RT installed on a regular PC. It seemed to work ok and did some simple tests using the network card, but never used it for anything serious/production, more just to see what was involved. I believe that doing this might be in violation of some licensing agreement.

ah ok, that explains things. No there is no LAVA discord.

I only know of one general LabVIEW discord server. I am not sure what the top one in your picture is! That link works fine for me (in an incognito session)

You are writing text into the spreadsheet, maybe that is why your formulas are broken. Have you tried writing numbers instead?

@Zyl that link should not expire, does it not work for you? (https://discord.gg/sSMm42aYvW)

Hi Dasha, we have a special channel for user groups over on the Discord. Would you be able to post it there also? Here is an invite to the Discord if you are not already a member: https://discord.gg/sSMm42aYvW

I am pretty sure Rolf knows it is not any kind of criticism.

@Rolf Kalbermatter I know you did not mean this, but I love it!

Sure I know this pattern well, just prefer to have a single "mailbox" type event inside my actors for messages into the actor. I don't want to deal with the drama and scripting just to be able to have different typed events. My layer above the variant is all typed, so I don't really have an issue with converting variants to their real types. But of course everyone must do whatever pleases them most. I have way that works for me, my team, and the kinds of things that we build, so have no need to make it more complicated.

While I appreciate dynamic languages and the flexibility they offer I think this is pretty bold blanket statement and is totally context sensative. Would you want to write a driver for your GPU with a language that does not offer strict typing?

I am not against your idea of adding a bit of love to the events implementation.

Not for me though, my low level messaging uses events and that is just waaaaay to much drama to have separate events for every message. I wrap it up a layer with typedefs though, just the data is transported in a variant.

LabVIEW 7.1 and python 2.7? Yikes!

yup, exactly how I do it too. For me the notifier has a variant data type so (unfortunately) needs to be cast back to real data when the return value comes

I can completely believe that C++ graph. It is probably not marching to oblivion, but is surely marching to some low constant value. Very few greenfield applications are started in C++ (apart from some computer games using Unreal I suppose)

@hooovahh this is literally perfect 🙂 (I see my rusty memory got the roles mixed up).

There is a public (but not official NI) fix for this, but I have not tested it personally. https://github.com/illuminated-g/lv-2022-apply-icons

Unfortunately this is a known issue with recent versions of LabVIEW and will only be patched in 2024 I think. I will try and dig up more infomation.

This sounds like the perfect candiate for that meme of Orange County Choppers where the dad and the son are yelling at each other: Son: JUST RELEASE IT ALREADY Dad: ITS NOT PERFECT Son: NOBODY WILL GET TO SEE IT OTHERWISE Dad: I DONT CARE My 1 cents into the issue. The whole spirit of modern software dev is just to hang your dirty laundry out to dry for anyone to inspect. I think this is a change for the good. @ShaunR I think you have very little chance of finding someone to maintain (I presume) some very old code , in a state they have never seen, likely with heaps of strings attached, in a super niche area of interest.

Take a look here: https://github.com/VITechnologies/RemoteLabVIEWInterface It works great! It uses JSON to pack up stuff from python and send over ZeroMQ.

I am definitely not an expert on this kind of stuff, but I think you would first "create" a datastructure big enough to hold your image in LabVIEW. The type does not actually matter as long as it is big enough (1 byte * width * height) and then pass that into your DLL call as the first input parameter, followed obviously by the width and height. After the DLL call the data should now have been copied into that datastructure (i.e. the wire itself will have the image on it). I get easily confused with pointers to pointers, so might have this completely wrong. Sorry I have not explained this very well. Can you attach your DLL?

I think there were 182. Everything was video recorded and after editing will be posted on YouTube. Expect something in about six weeks.

ok, and what have you tried so far? What would your rough python code for this look like?