MikaelH

Here is an updated version and more complete version of this LINQ VI LcArray_LINQ.vim

I just have to add this fun vim using your (@drjdpowell) SQLite library. It's LINQ for LabVIEW (I only spent 20 minutes on it so it's a bit rough) LcArray_LINQ.vim

If you Defer Panel Updates, with that save time?

You can fix it in 2 ways. 1. Force open the VI and change the dll call (LabVIEW.exe) to not run in the user interface thread. I've tested this and this will speed it up 1000 times or so but... this could crash LV if this code is running in any of LV's special Application instances like Project Provider App instance (And that is where I need the performance improvements in the OpenGDS UML Modeller). 2. Yes, use a Map or Variant look up. See example VI GetTextRect_AnyThread.vi

Looks Cool Maybe we should make a public framework for this and a big open source library of UI components. FYI you don't need to wire an empty class constant to the create methods 🙂

Many controls have invoke nodes like this to convert the click position to more meaning full info, e.g. where in the X/Y plot you click.

This is how you do it (the right way) 😉

I've not dared to outsource the building to a build server yet, mostly because we get these strange build errors from time to time, like "This VI broke during the build". Also since my team does quite many builds and we would need multiple build servers since a build could take an hour, and sometime I need to build 6 version right away and that could lock up the build server for 6 hours. But if you get it working close to 100% let me know, then we might switch over.

If you switch the disabled structures, it shows you how it works better. Using the Graph.Plot feature is just an option, I would probably use a separate Picture conttrol to the left of the Graph that hold the titles. Or when we want to have nice/different types of plot we use a WebBrowser container with html/javascrip code.

So 2014 should be good then 🙂 Maybe it's time to think about upgrading 😉 2020SP1 is Awesome, especially now with Interface support 🙂 Horisontal BarChart-2014.vi

Is 2016 okay? Horisontal BarChart-2016.vi

You can do something like this: Horisontal BarChart.vi

Thanks, I missed that. Strange that is allows any text and messes up the JSON content completely if it's not valid json.

Hi, I do like the new “Retain All Errors” in the Merge Errors, it coverts the Error source to an JOSN array of errors. With that change NI added some extra JSON Error VIs like the Write attribute. But I can’t get those VIs working? I couldn’t find anyone else complaining about this, sure I can just fix the issue myself since the VIs aren’t locked. Are anyone using these VIs?

You can do this. I thought that was the main reason for adding interfaces ☺️. BTW, if you're using LV2020 and classes, the new OpenGDS beta version makes it easy to work with interfaces 🙂

We modify code while LV is running all the time 🙂 We even have a Quick Drop shortcut that toggles a Sub-VI's Loading Option between "Load with callers" and "Reload for each call".

Hi, I just posted my GOOP Training course material here: https://forums.ni.com/t5/GDS-Goop-Development-Suite/GOOP-Course-Material/td-p/4101113

Same here. It locked the whole OS for some reason when I start NXG.

And when can we add G code extension to NXG's IDE? I'll move over when I get GDS running there 😉

I would use Active objects. Using the OpenGDS tool I created this in no time, see attached project. ActiveObjects.zip

We use 5000-5999 for project/application specific Error codes, and then different ranges for other common components. But for an instrument drivers, we might use one of the existing LV-error codes, and for that we use a small tool to find a good error code. ErrorCodes.vi

Maybe this shows when to use it 🙂

Company made version, based on Ref-based OO and active objects.

I remember that I had to change my code using the "cmd /c" when changing over to Win10 from Win7. Before I didn't have the "working directory" wired instead I specified the full path in the command. e.g. cmd /c "c:\Temp\file.bat" Are you running WIn10?

There is a brown/private property node that can suppress all dialogs. If you don't have access to this property node, you can find a sub VI that does this for you here.