LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
tst

Automatically skip password protected vi.lib VIs when searching

Status: New

When you do a search for something in the hierarchy and you have a password protected VI, you get this dialog:

 

 

 

 

Often (for example in this case) we don't have the password for the VI and never will because it was developed by someone else. So why not allow us not to see this in the first place?

 

  • First idea - Don't display this at all for VIs in vi.lib. Just skip them.
    Presumably before LabVIEW ships the VIs aren't locked anyway, so the LabVIEW developers shouldn't have a problem, and if they do, let them do a programmatic unlock. The users shouldn't be the ones to suffer.
  • Second idea - Generalize it a bit more. Allow us to have a configurable list of folders where the search won't bother to try and unlock VIs (so that if we have locked code from other vendors, we can discard it as well). The default folder for the list should be vi.lib.

___________________
Try to take over the world!
17 Comments
Raeff
Member

We have one pw-protected VI in our project and I need to do many searchs...

Each time I need to click on Skip. I really gets annoying when it's the 100th time you're doing this.

 

It seems to me tha this feature would not be a lot of effort to build into LV, but then I'm not NI R&D...

Still cross my fingers that it will be included in the next couple of years.

 

Kudos please...

Working with LV2011, LV2018 and LV2020
MGiacomet
Member
Seven years and counting... Hello, NI? Small things like these are what increase productivity not some fancy new "feature"
tst
Knight of NI Knight of NI
Knight of NI

I actually haven't seen this dialog in a long time, probably because at some point NI added this checkbox, which LV seems to remember:

 

find filter.png

 

That basically seems to implement the first version of the idea.


___________________
Try to take over the world!
MGiacomet
Member
Well, "thanks", tst... So NI implemented something that partially hides the issue? The problem persists.
AdarshaPakala
Member

I think this is a very useful and time saving. 

Eric_MyNi
Member

This is still a very real problem.

 

An example of a subvi that is not avoided by clicking 'Ignore VIs in vi.lib' is 

 

C:\Program Files (x86)\National Instruments\LabVIEW 2019\resource\dialog\lvconfig.llb\LV Config Read Boolean.vi

d.w.b
Member

Consider kudoing a related idea to be able to "Find All Instances" of the password-protected file as a workaround. If many searches are anticipated, it would be helpful to close the password-protected VI so they will exclude it and not prompt. However, closing the window leaves it in memory if it is a sub-VI. Depending on what is being search for, the developer may be willing to close its callers as a workaround.

 

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-quot-Find-All-Instances-quot-on-a-password-prot...