Jump to content
prettypwnie

LV 2016 Different Behavior For Dynamic Dispatch (possibly bug?)

Recommended Posts

I've run across an interesting difference in how LabVIEW 2016 works with dynamic dispatch VIs compared with 2015. If you put the class wire on a shift register of a loop and then have an event structure inside it and in one of the event cases instead of wiring the shift register through, you wire whatever value was originally put into the shift register through (you might do this if you're making a dialog to configure the class and want to let the user cancel it without affecting any changes) it breaks your VI - it doesn't consider this to be a "good enough" way of wiring your dynamic dispatch input to the output. However, if you have this same code in LabVIEW 2015, it works perfectly fine.

See attached code for an example - if you open it in 2016 the run error is broken, in 2015 it is not. It is the exact same code.

Does anyone know if whether this is a bug or just new, intended behavior?

 

--Hope

Bug Test.zip

Edited by prettypwnie
  • Like 1

Share this post


Link to post
Share on other sites

I'm not aware of any intentional changes in LabVIEW 2016 that would cause this. Please post the question to the LabVIEW forum on ni.com so an AE can investigate the issue and file a CAR if necessary.

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.