todd Posted March 29, 2013 Report Posted March 29, 2013 I've been packaging up all my reuse libraries with VIPM (Free). I want to avoid accidentally modifying those libraries while using them in another project. In a Post-Install VI, I iterate through the list of "Files Installed" and lock then save all .vi, .lvclass and .lvlib files. An up-side is that when I open a reuse VI or class, I know right away by its appearance. What are the down-sides? Quote
crossrulz Posted April 1, 2013 Report Posted April 1, 2013 People can see the code. Though, that's not really much of a downside. The other small issue is that people can go in and change the setting and then edit the VIs. Again, I don't see that as a major down side assuming you trust those who are using the libraries. Quote
todd Posted April 1, 2013 Author Report Posted April 1, 2013 I do want the code to be visible. I am not currently worried about the setting being changed. Primary concern is that someone (including myself) opens a VI and knows right away that it's in a library/package. Thanks for your input! Quote
Aristos Queue Posted April 2, 2013 Report Posted April 2, 2013 That option was designed for the purpose you are putting it to, so I wouldn't expect a downside. :-) Quote
todd Posted April 3, 2013 Author Report Posted April 3, 2013 Excellent, thank you. For the record, there has been no trouble locking every .vi, .ctl, .lvclass and .lvlib file - in any order. Quote
soupy Posted April 29, 2013 Report Posted April 29, 2013 it would be nice if the "locked" setting was available as a standard VIPM package setting so you don't have to keep track of it in postbuild scripts. have you suggested this to them on their idea exchange? Quote
todd Posted April 29, 2013 Author Report Posted April 29, 2013 I have not. There's some kind of protection tab in the Pro version, though. Maybe it's in there. Quote
soupy Posted April 29, 2013 Report Posted April 29, 2013 I've got pro. I don't think it's the same as you're doing. It requires the NI licensing and activation toolkit. Not going to be buying that for something that is easily accessible via property nodes. Quote
todd Posted April 29, 2013 Author Report Posted April 29, 2013 Looking again, under Source File Settings, there's an option to add a password. That's not available in Free. Does Pro allow you to select Password Type "Custom", then leave a blank password? Quote
soupy Posted April 29, 2013 Report Posted April 29, 2013 putting in a blank password make the "password type" switch back to "none" it may work if they add "locked (no password)" to the "Password type" dropdown Quote
todd Posted April 29, 2013 Author Report Posted April 29, 2013 Ok. Still Pro, but the idea is here: http://ideas.jki.net/topic/167870-allow-locked-no-password-protection/. Quote
Michael Aivaliotis Posted June 7, 2013 Report Posted June 7, 2013 A follow up to this. I've added this feature in VIPM Pro. It's not available in the public release but you can get it in our VIPM Labs section here: http://support.jki.net/entries/24071293-VIPM-Labs . Even though it's not a public release, we are fully supporting it just like any other release. It requires the NI licensing and activation toolkit. Not going to be buying that... Just wanted to make a correction. The licensing and activation toolkit from NI is free. 1 Quote
soupy Posted June 7, 2013 Report Posted June 7, 2013 this is great! i'll be testing this immediately! I'm guessing that this will eventually be released publicly once your release cycle comes around? Quote
Michael Aivaliotis Posted June 7, 2013 Report Posted June 7, 2013 I'm guessing that this will eventually be released publicly once your release cycle comes around? Yes, correct. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.