Jump to content
Wouter

OpenG / Polymorphic & Malleable VI's?

Recommended Posts

First question,

Is OpenG not available for LabVIEW NXG 5.0? When I try to install it via the NI Package Manager I see version 3. Then when I want to install it, I see that the NI Package Manager wants to install LabVIEW NXG 3.0... so I understand that OpenG is only available for LabVIEW NXG 5.0? 

 

Second question, (cross post from https://forums.ni.com/t5/LabVIEW/LabVIEW-NXG-Polymorphic-amp-Malleable-VI-s/m-p/4047507#M1160978

How can I create a polymorphic or malleable .giv in LabVIEW NXG? In NXG they are called "overloads"

The only information I can find is: https://forums.ni.com/t5/NI-Blog/Designing-LabVIEW-NXG-Configurable-Functions/ba-p/3855200?profile.l...

But it does not tell or share how to do this in LabVIEW NXG? Where can I find this information? Or am I just missing something?

 

Images (w.r.t. first question)

 

 image.png.6bf0279de82cd71177439aa4b6601507.png

 

image.png.5ef0c8e4534ef0ced6e7b9236e376c1b.png

Share this post


Link to post
Share on other sites
39 minutes ago, Wouter said:

Second question, (cross post from https://forums.ni.com/t5/LabVIEW/LabVIEW-NXG-Polymorphic-amp-Malleable-VI-s/m-p/4047507#M1160978

How can I create a polymorphic or malleable .giv in LabVIEW NXG? In NXG they are called "overloads"

The only information I can find is: https://forums.ni.com/t5/NI-Blog/Designing-LabVIEW-NXG-Configurable-Functions/ba-p/3855200?profile.l...

But it does not tell or share how to do this in LabVIEW NXG? Where can I find this information? Or am I just missing something?

In the article it says: "The ability to create modes and overloads isn’t publicly available in the newest version of LabVIEW NXG; however, we’re looking to extend these features to our user base soon."

  • Like 1

Share this post


Link to post
Share on other sites

Currently NI's package manager is less suited to distributing LabVIEW reuse in NXG, when compared to VIPM in LabVIEW 20xx.  This is partially because in NIPM the package must be built for a specific version of NXG.  So a package made for version 3.0 can't be installed in version 5.0, until the creator of the package updates it and rebuilds it for version 5.0.  For reuse to be more adopted in NXG, this limitation needs to be removed.

Share this post


Link to post
Share on other sites
32 minutes ago, hooovahh said:

in NIPM the package must be built for a specific version of NXG.  So a package made for version 3.0 can't be installed in version 5.0, until the creator of the package updates it and rebuilds it for version 5.0.  For reuse to be more adopted in NXG, this limitation needs to be removed.

There's an Idea Exchange entry about this for LabVIEW CG, but it really should extend to NXG too: https://forums.ni.com/t5/NI-Package-Management-Idea/Install-the-same-package-to-multiple-versions-of-LabVIEW/idi-p/3965419

  • Like 1

Share this post


Link to post
Share on other sites
16 hours ago, JKSH said:

There's an Idea Exchange entry about this for LabVIEW CG, but it really should extend to NXG too: https://forums.ni.com/t5/NI-Package-Management-Idea/Install-the-same-package-to-multiple-versions-of-LabVIEW/idi-p/3965419

Well it kinda does apply to both considering NIPM should manage both CG and NXG. I've heard through a reliable source that NI is seriously intent in solving this problem in NIPM for both CG and NXG.

Share this post


Link to post
Share on other sites
23 hours ago, LogMAN said:

In the article it says: "The ability to create modes and overloads isn’t publicly available in the newest version of LabVIEW NXG; however, we’re looking to extend these features to our user base soon."

Thanks! Totally missed that.

 

19 hours ago, hooovahh said:

Currently NI's package manager is less suited to distributing LabVIEW reuse in NXG, when compared to VIPM in LabVIEW 20xx.  This is partially because in NIPM the package must be built for a specific version of NXG.  So a package made for version 3.0 can't be installed in version 5.0, until the creator of the package updates it and rebuilds it for version 5.0.  For reuse to be more adopted in NXG, this limitation needs to be removed.

So who is currently the creator of OpenG? And is this maybe something I can do myself?

Share this post


Link to post
Share on other sites
On 5/12/2020 at 1:21 AM, Wouter said:

So who is currently the creator of OpenG? And is this maybe something I can do myself?

Send an email to: jim.kring@jki.net

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.