Jump to content
Ryan Vallieu

Malleable VIs - Nested Malleables - Broken Class adaptation in Malleable VIs in 2019

Recommended Posts

I have seemingly found an issue with the shipping example code for Nested Malleable VIs.  Another user has verified that he saw the same behavior in 2019.

 

I am working through the examples and the presentation from NIWeek 2019.  In running the Lesson 2b code (C:\Program Files (x86)\National Instruments\LabVIEW 2019\examples\Malleable VIs\Nested Malleable VIs) I found the Equals.vi in the class was not being leveraged and the search failed.  When I went to my LabVIEW 2018 machine and ran the Lesson 2b.vi the code worked to find the element by correctly leveraging the in-class Equals.vi.

One difference I see is that in the 2018 example the Equal.vi is in the example folder with the code, and in 2019 the Equal.vi has been moved to VI.lib - otherwise the code looks to be the same.  The Equals.vi code looks identical, and the calling VIM look identical.  I posted on the LabVIEW NI.com forum here: 

https://forums.ni.com/t5/LabVIEW/LabVIEW-2019-Malleable-VIs-Shipping-Examples-Lesson-2b-Nested/m-p/3966044/highlight/false#M1129678

 

I am trying to determine what may have broken or changed between the implementation in 2018 and 2019, visually the code looks the same.

Edited by Ryan Vallieu

Share this post


Link to post
Share on other sites

Broken Class adaptation in Malleable VIs in 2019:

There is a difference in the code that I missed before.  See the attached file with the screen shots.

In LabVIEW 2018 Example Code the top level Search Unsorted 1D Array.vim has in TSS Case 1 the normal Search 1D Array function, but the start index and element are UNWIRED - thus this case would be broken.

In LabVIEW 2019 Example Code the top level Search Unsorted 1D Array.vim has in TSS case 1 the normal Search 1D Array function, but the start index and element are WIRED - thus this case is not broken.  The Assert Structural Type Match function is only configured to look at the Functor input - and thus with it unwired this case is selected.

Malleable Nested VIM - Lesson 2B Convert to Instances.pdf

Share this post


Link to post
Share on other sites

Rearranging the cases in the Type Specification Structure so that the default LabVIEW function is the LAST case restores expected behavior (I think)...not sure if this is what was intended...

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.