MikaelH

Mostly we use 3 levels for the instrument driver (InstrumentBase <- InstrumentType(e.g. PowerSupply) <- RealInstrumentDriver (but also a simulated type) We currently have 398 classes in our instrument hierarchy, 60 different InstrumentTypes such as: (TemperatureControllers, Robots, WeldingLasers, GlueDispensers, StepperMotors)

I've had issues on Windows 7, but no issues on Windows 10 yet. When our SW needs it and can't find it we let the user install it on the fly running this exe file: MicrosoftEdgeWebView2RuntimeInstallerX64.exe ..and that has never failed yet, maybe it could cause issues if you've installed the 32 bit version first?!?

FYI, I've found the WebVIEW2 WebBrowser integration into LabVIEW + a fancy DataGrid JavaScript library is a much flexible approach. We've posted the LV-64 bit supported WebView2 support here: https://github.com/ANSCenter/LcWebView2 I use http://tabulator.info/ to make nice DataGrids in LabVIEW.

Here is a start of the color selection, can someone see if we can make it faster? ColorPicker_GUI_DrawColorRectangle.vi

I just have to implement it first 🙂 Not sure which UI style would be the best

I would make my own popup, so it looks better, something this:

You just need to add a magical VI here to get it working:

I have several instances where I get null back for different datatypes, what I have to do is just to ignore the Errors from the JSON VIs. So it will convert everything it can' but when trying to convert NULL to a string it will be empty or for an int it will be zero. Ideally it would be good to be able to say when you find Null for: A strings use "" or "NULL" A INT use 0 or -1 For DBL/SGL it uses NaN and that is prefect.

What you could do is to start just using the Singleton Class template, sure it's based on OO, but you don't need to think of that, it's just like a action Engine, but instead of having everything in one VI, you can add several VIs (methods) to the Singleton library (lvlcass), and just because they belong to the same class they all share the same data. You just have to learn how to use the IPE structure to read and modify the shared data.

I guess Vision Express, is using the Express VIs for vision?!? First never use Express VIs ;-). Second open the example VI of tracking objects: Not sure if it's in LV2019, I'm using 2020. LabVIEW 2020\examples\Vision\Tracking Third, start using LV 64-bit,

So always use Singletons instead of FGV when I know I only need one instance of an object, i.e. one memory space that should be shared in my application. Just like a global variable, but using the class to control access to the global data. I've attached a Singleton example that should get you going. The OpenGDS toolkit generates these classes and Access VIs (methods) to make it easy for you. Also I talk a bit about the Singleton pattern and how to create that here: Singletons.zip

I'm very happy for you. Thanks for all your support over the years. Anytime you need any help, just let me know.

If you use reference based OO, then you could avoid extra data copying. If you want to use OO you get lots of extra IDE help function with this free add-on. http://opengds.github.io/

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