Jump to content

Here's a way to open VIs without file dialogs for missing subVIs


Recommended Posts

Both, pal! But in LV13.0bxx era, I asked the same question, and the unofficially-reworded response was "yep; we [NI] changed this because previous to this change the AppRef was leaking; just keep it open til you've done what you need to do with the newly-created VIRef, then `Close Reference` on the AppRef and it'll work like it used to, just less-leaky".

I've used that guidance for 2yrs now with success; your independently-discovered `*Edit` is the correct way to use this method now.

 

Does this mean old code will be 'broken' in 2013+?

Link to post

Does this mean old code will be 'broken' in 2013+?

 

Likely; mine was, and it appears @hooovahh's was also. One patch for backwards compatibility is to dynamically dispatch via CBR a version saved in LV for <2012 and another for >=2013.

Link to post

My use was I had some tools that prepare code for getting ready to package it up using VIPM.  This is the same tools I've used on things like my Variant Repository and Circular Buffer.  I would run a VI that opened the code, removed compiled code, turned off debugging, automatic error handling, lock the VI (no password), and add some text to the VI Description.  So for me I wrote the code to work in the oldest version of LabVIEW supported.  So when I was packaging up code that worked in 2011 and newer it worked fine.  When I had a package that needed to be 2013 and newer I tried running the same code, which is when I found this change.

 

Good to know I'm not crazy.  Also I guess its a good thing this is a private function.  Finding bugs in private functions makes me feel like NI did the right thing by not making the function public.  But I'm sure we have all the bugs worked out now so it can be public right....right?

 

Related idea exchange.

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Open-VI-reference-without-refees/idi-p/2329706

Link to post

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.