SAPHIR - Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

VI Tree is password protected

Solved!
Go to solution

Hi There,

I was testing out the new SQLiteVIEW toolkit (v1.0.0.38) and was surprised that the VI Tree was password protected, especially since it's a public VI of the library.

VI Tree - Password Protected.png

Was this intentional or an oversight?

Thanks,

-Jim

BTW: Great job packaging this up with VIPM.  I like the integration with the LabVIEW 2010 add-on activation manager.

JKI Blog
0 Kudos
Message 1 of 3
(3,517 Views)
Solution
Accepted by topic author Jim_Kring

Hi Jim,

Actually, this is both intentional and due to an oversight.

This intentional because in the state of the "development" of the VI tree, I think he won't be helpful for end-user.

This is an oversight because, as you notice, it's a public VI, so if I don't want to expose it I should not add it to the package.

Questions related to yours

  • If I want to add a VI Tree to an add-on, were it would be the best place in LabVIEW ? in the function palette, in examples, in an other place ?
  • Do you think VI tree can be helpful for end-user ?

Regards

Olivier

Olivier Jourdan

Wovalab founder | DQMH Consortium board member | Certified LabVIEW Architect |
0 Kudos
Message 2 of 3
(2,092 Views)

Hi Olivier,

Thanks for the info.  I would just make the VI Tree "private", if end users are not intended to be able to access it. (Since this will hide it in the library, since the library is locked.)

If you do want to make it available to end users, I do like putting it in the functions palettes (as is commonly done for instrument drivers).  I do think that they can be helpful, if organized properly.

That said, the value of a VI Tree is somewhat diminished, now that VIPM makes it so easy to get VIs in the palettes and install examples.  So, maintaining a VI Tree can be a bit redundant.

I'm sort of on the fence...

Thanks,

-Jim

JKI Blog
0 Kudos
Message 3 of 3
(2,092 Views)