Neil Pate

Sorry I thought I had replied here, but it looked like I did not click Submit! Thanks for everyone's comments. I have passed them on to my customer.

A bit more information. According to the Dependencies application the LV2020 also has a dependency on this System.dll that is located in the GAC. I have tried copying that DLL to various locations (I think I am not supposed to because this is system stuff!) but it still gives me the same error.

Recently I have tried to package up some code as a .NET Assembly. I managed to pack some pretty complicated LV2019 code (including some LabVIEW classes and dynamically called code) into an assembly and was able to call it just fine from a simple C# console application. However, this does not work when I moved over to LV2020. To make things simple to try and get to the root of it I created the simplest possible example I can think of. One copy is in LV2019 and it works fine, the other is LV2020 and it does not work. The assembly builds fine in LV2020, and indeed is callable from LabVI

One of my old customers is having an issue with the TSM-1017 losing its ability to be calibrated. The system runs on a cRIO and the screen is attached with a USB cable as well as the DVI cable. On Linux RT there is an application you can run that brings up a four point calibration, but apparently this application does not run anymore. This did all work once upon a time, but the system has been out of my hands for a very long time. NI support gave some very manual linux-ey commands to reinstall drivers or something, but I do not think this worked. Has anyone come across a situati

https://meh.com/forum/topics/building-the-plane-on-the-way-up tl;dr the ground based decoder for some of the comms on Voyager was built *after* the craft was launched, and it still to this day reliably receives data. Wow!

Posted here: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas/tab/most-recent There is a video linked in that post that pretty simple shows the behaviour. It is quite nice to use. If you like it please add your kudo on the Idea Exchange!

Exactly why we need NI to buy in to the idea, otherwise it will never get off the ground.

Excellent idea, I have added my kudo! I don't think this will get much traction from NI but it would be really nice to see this as something semi-official. Once you know what you are doing it is not super complicated to get RT linux running on a desktop.

I have created some code that allows me to translate the GUI language on the fly at runtime. Is anyone else interested in this? At the moment it is a bit coupled into my actual application but I think I can extract the relevant bits. It supports pretty much any latin codepage language and once upon a time did also support Chinese (but I have not tested that in quite some time). Obvious disclaimer here: I just want to share what I made, but use at your own risk, and I am definitely not a UTF8/16 whatever expert so there might be some stuff that is just plain wrong.

I am not *that* paranoid, but certainly I like to push my work at the end of each day. I am not actually anti-git, it is just taking me a while to get used to its best practices and nuances.

I guess what I mean is I find it strange that people would even have local branches that are not pushed to the server. Maybe I am just paranoid about my house burning down, my computer getting stolen of my hard drive dying. For me one of big benefits of cloud based VCS is that I almost always have an up-to-date geographically distributed copy of my code.

The thing I still find a bit strange is how it is possible for the remote and local branches to be totally different (even different names). I totally get that the local branch can be out of sync if you have not done a push/pull to the server, the thing that seems weird to me is that the local can have a totally different structure. This is just something I need to get used to.

This morning I finally realised why I semi-regularly get into a detached head state (I think I know why...). In git there are several different options for checking out a commit (checkout commit, checkout branch etc) and I never really paid much attention to the subtleties of these. As far as I thought they all did the same thing, that is revert the local code to the state of that commit. It turns out that my understanding was flawed, and every time you check out a single commit (rather than the actual branch) the current state will not point to any particular branch and you will be in t

I use InnoSetup for a custom installer and I also install the 2019 runtime this way. It may not be the "right" way to do it, but the way I solve this problem is to manually extract the runtime installer and then just include that directory in my installer and run the Install.exe from the installer.

I think LabVIEW is going to be around in some form for at least another ten years, primarily due to how entrenched it currently is in the niche it fills. However, if I was starting my career again in 2021 I would definitely not choose LabVIEW as my primary language of specialization. I think the poor decisions NI have made over the last ten years will lead to its irrelevance/obsolescence, which I am genuinely saddened by. It pains me to think where current gen LabVIEW could be if the money and time funneled into NXG had been put to overhauling current gen.