MikaelH

Hi Yes start with the Projected Provider documentation and the look through examples (e.g. the OpenGDS). I started in LV8.2, and lots of the issues I had, have probably been fixed since then. But one thing to remember is that it doesn’t (or at least didn’t) like to do things in parallel. E.g. if you add an item to the project tree (e.g. a new class), then that could trigger some other project provider calls (e.g. a new item added to the project window), so I had to add a small wait after those functions. If I didn’t do that LV could crash from time to time, that’s why you can find a lot to 150ms wait in the Open GDS code. Debugging the project provider code is a bit tricky. You can save a Break point on the BD of the provider VI, and then restart LV. The first time the code hits that break point the You can debug the code, but after that you Can debug the VI anymore, you have to restart LV again. Make sure you open VIs in the correct application instance if you want to modify them, and always remember to close all the referees opened in the provider VIs.

Is this what you are doing? SubPanel_Main.zip

It works great for me, if you right click and select: "FatBits", it becomes a bit bigger and could be a good tool to create a 32x32 icon (That's the only size it supports). There are no Property/Invoke nodes for this control, and Value change event don't seems to work 😞

Why not merge it into OpenGDS's wire editor and create a Pull request.

Sorry missed the lvclass files. BTW, I used OpenGDS to create the class and methods. XY-Shape.zip

Try something like this 🙂 XY-Shape.zip

No only 1.2.38 has the strange freeze.

FYI, version 1.2.38 has an issues when creating Override methods. Please use the latest one 1.2.39 https://opengds.github.io/ You won't believe what I had to do to get it working ;-), coding VIs that runs in the project provider application instance is not always easy. A VI that works fine when you run it normally, could still crash/freeze LV when it's running under the project provider application. I hope it will be easier in NXG.

I would love to get more time to show everyone all the nice and fun feature that exists in the GDS tool. If anyone like to help please feel free :-). I'm aiming to document the "Convert Text based code to LabVIEW" next. You can always test it and see if you understand how to use it... You can google come Java or c# Design pattern examples (e.g. Observer pattern), and convert those classes straight into LabVIEW. I also want to document the API VIs, if you haven't tested them you can find them + examples here: LabVIEW 20XX\resource\Framework\Providers\Open_GDS\API

The new version is ready for download under Untested Version https://opengds.github.io/

I don’t agree ?, you just need to know where to look ? Every design pattern that is added to a class, have the ability to add new Method templates and you’ll find them here. This is the same if you add the Active Object Design pattern there is a method templates that helps you send and receive a message form the active process. BTW, I've created the new version with new templates, I just need to upload them, I let you know when it's done.

The GetAttributes checks the DVR ref and generates a 1556 error if the DVR is invalid, but of course the DVR Ref could be killed externally between the Get Attribute and when the IPE node is executed...there is always a chance.

Some test code I made of doing 500 Get Attributes of a class with some large data sets. I would try to avoid having to much data in the Attribute, but if I need it I might user the Reference Variable Design Pattern GDS can apply to a class. GetAttribute.zip

You are right the read will be much faster if you use the DVR and use the IP Structure to just extract the element you need form the cluster. I'll update the templates to use this method.

Great job, look awesome

It's hard to test that VI since it requires a camera (and one VI s missing). But I haven't had any issues with the Scroll bar (at least when you figured out how the property node option works). If you can make some test code it will be easier to help you.

Sure I'll add it, I thought everyone had a VI like that. We use it to indicate that the developer is aware that an error could be generated at this point in the code. It helps when we do code review.

This is how I clear errors.

Can't you just use this method? GOOPUtil_GetParentClassesHiererchy.vi

You can alwasy look at OpenGDS and the examples it comes with and the demo videos :-) http://opengds.github.io/ http://www.youtube.com/watch?v=UcUj_Gl1JdI https://www.youtube.com/watch?v=hdcHYS_ZFr8 http://www.youtube.com/watch?v=_BvIiU2VMAU http://www.youtube.com/watch?v=ZWeO_wPe-VQ http://www.youtube.com/watch?v=OunqB9UdR6o http://www.youtube.com/watch?v=VncaD_pKe_s http://www.youtube.com/watch?v=i77lHDIMs_s

Hmm, you are probably right, we only had this issue on all out W7 PCs.

Have you tried appling patch: KB2999226-x64.msu ? That fixed our problem. https://support.microsoft.com/en-au/help/2999226/update-for-universal-c-runtime-in-windows

Just an update, NI has found and fixed my issue, it's just a matter of time when we'll get a patch for this, maybe I have to wait for the Service pack before I can migrate to 2018.

I've done lots of small mass compiling to see if that solves the issue. But no luck yet, but I'm getting closer it looks like it freezes when it load projects using the Vision module. We need to use 64 bit on quite a few test system when we use lots of vision stuff and/or testing multiple units at the same time (capturing heaps of data, maybe more than we need) And some larger project can't even build an exe, LV runs out of memory during the build process.

I've now done a source distribution of all the code and the code open in LV2016, but not LV2018. I'll zip this up and send it to NI for investigations. (I'll just remove all sensitive IP stuff, even with missing VIs LV2018 should freeze but it does) I'll keep you posted about the progress.