mabe

I confirm that this license is nearly identical to the standard EULA we use for our commercial products. Some wording is not applicable to a distributed palette of VIs like this. Our intention was to share a few reusable tools, used internally, with the community. Ideally, we should have released them under a standard open-source license such as MIT or a similar option. These VIs have been released “as-is,” without support or any guarantee that they will function for your specific use case. You may need to troubleshoot or fix any issues on your own. Feel free to use them in any context. I’ll look into whether it's possible to update the packages on the tool network to replace the current license with a more standard open-source one.

Wow! Maybe next time they will default the VIs front panel to pure white too. BTW, I don't understand why (after nearly 35 years) the block diagram color in LV is still part of the VI instead of an IDE preference. Even if I change my local setting to some gray for my VIs, I still get tons of VIs from other developers with the default burning pure white.

Here is the new revamped UI of NI TestStand 2020: Maybe it's just me, but I find it very difficult to work with the new color scheme of NI TestStand. My eyes are burning after few minutes... Am I the only one? Here is the default UI colors of VS Code, the super popular code editor from MS. So much less stress for the eyes. Hoping for dark mode NI TestStand in a near future...

Just a little clarification. The Averna NotifyIcon is surely inspired by the same NI example found on ni.com but it is not a rebranded/repackaged version of the Stinus Olsen library posted on LAVA. I've made the Averna implementation as an internal reuse library a long time ago. It was posted few years later on the LV Tool Network.

Hi, I have found the same leak in LV 8.5 or 8.6 while using the beta version of the Desktop trace toolkit few years ago. At that time I have oppened a service request on this and a CAR was maybe raised but I not sure. I think there is no way to avoid the leak...

Hi, Did you tried to add the key "hiderootwindow=true" in the INI file of your EXE? Mathieu

Hi, I have seen this behaviour before. You can verify with NI but I think (at that time) it was confirm as a bug by NI

Hi, This acticle shows another way without .NET http://digital.ni.com/public.nsf/allkb/935...625711E0055F1FA Mathieu

Hi I have got the same error when I went from 8.2 to 8.2.1. So it may be an upgrade bug. It was not a big problem for me since it was just the beginning of my project and there was no release yet. So I just use the new datalogs created in 8.2.1.