LabVIEW
Applying same window appearance to all VIs
Hi Vinny,
@VinnyAstro wrote:
I'd like to apply password protection and window appearance to all my "User interactive" - VIs, so they all look the same (no running nor abort button, resizing, scroll bars etc.).
Problem is I have quite a few of these and applying these parameters can be annoying...
Is there a way labview allows you to do it for all VIs at once?
Should I use scripting (never done any before)
When you want to automate the LabVIEW IDE then you should use scripting…
On "password protection": the current password system of LabVIEW is rather unsafe. When you don't want to show code to your users then you should create executables for them!
You may also strip the block diagram from a VI, but be sure to keep an "original" backup! (As you already should by using a SCC system of your choice.)
@VinnyAstro wrote:Should I use scripting (never done any before)
I think this is all VI Server, not scripting.
Not that it makes much difference, 'scripting' is basically VI Server with advanced options...
Keep in mind that
1) with scripting on, VI Server can be overwhelming, and
2) with scripting off, you might not be able to do things you want to do, and
3) even with scripting on, you might not be able to do some things...
Search LabVIEW like a graph! Hi Vinny,
@VinnyAstro wrote:
- What do you mean by striping the block diagram?
See this.
@VinnyAstro wrote:
- As for the password protection, how unsafe is it?
There are tools available online that allow simple&easy disabling of password protection of LabVIEW VIs…
@VinnyAstro wrote:
What does VI server do exactly?
I actually couldn't find much info on first researches...
First two hits on google:
Anytime you get a reference to a VI (static, by Open VI Reference or by any other means), and use a method or property, that's VI Server.
@VinnyAstro wrote:All I know for jnow is that it seems to allow me doing remote debugging and control, using shared variables etc.
What else?
No, that's not it...
Remote debugging could maybe be considered a subset of VI Server, but I'd not automatically call it VI Server.
Using Shared Variables is simply something else.
@VinnyAstro wrote:As for the password protection, how unsafe is it?
It's as safe as a lock on your front door. It tells people it's not allowed to enter. It doesn't stop burglars (very long).
@VinnyAstro wrote:Depending on the requirements I always prefer to send an .exe, but sometimes I have to send a Library for instance. I mean I am never doing big distributions anyway, it is always for one customer and eventually some modifications for a second or third one... And the password protection is rather for safety and warranty on our side (making sure they don't mess up with the code and the system isn't safe anymore) than anything else.
Either accept that passwords are just useful for protecting customers against their own mistakes, or send an exe or packed libraries.
Packed libraries are compiled, so you can have usable VIs, without distributing source code. It's a huge topic on it's own.
@VinnyAstro wrote:
@GerdW wrote:
When you want to automate the LabVIEW IDE then you should use scripting…
Understood. I need to take some time to learn scripting 🙂
I'd recommend you learn VI Server first... Scripting gets complex fast.
