Configuration VIs won't work with LLBs

[Rainer Ehrt]

Hi folks,
for keeping all application files together I prefer using LLBs.
Since using configuration vis (Functions>File I/O>Configuration file
VIs) I have the problem that these VIs are not able to open, read nor
write the config file into or out of a LLB.
Is there a workaround, or how do you folks handle this?
Another main reason for hiding the config files is to keep the users of
of manipulating them.

Ciao,
Rainer

[Brian_Vibert]

Maybe I'm missing something, but I thought that LLBs were only able to store VIs and CTLs. If you want to prevent the users from changing them you could hide them somewhere else. The other thing that you could do write a routine to encrypt/decrypt the file.

Brian

[Rainer Ehrt]

Brian Vibert wrote:

> Maybe I'm missing something, but I thought that LLBs were only able to
> store VIs and CTLs. If you want to prevent the users from changing
> them you could hide them somewhere else. The other thing that you
> could do write a routine to encrypt/decrypt the file.
>
> Brian

################

Hi Brian,
LLBs can store anything and keep files together in a easy way. For
instance, if you create a Run-Time-Menu for a VI, the aprobiate file
"Menu.rtm" is written into the LLB where the VI is in. I just figured,
that not all file I/O VIs can handle LLBs.
You can check this by starting Tools>VI-Library-Manager from the control
panel.

Ciao,
Rainer

[Brian_Vibert]

I've been unable to get LLBs to contain anything but files created by LV. Nor have I found any documentation saying that they should contain anything but LV specific files. A RTM is just another file created by LV.

Brian

[Joe_Guo]

write it as a binary file or encrypted text file, or write it to a location where people won't find it. The configuration file can't be modified because LLB can not dynamically grow and decrease in size.

Joe

[Rainer Ehrt]

Joe Guo wrote:

> write it as a binary file or encrypted text file, or write it to a
> location where people won't find it. The configuration file can't be
> modified because LLB can not dynamically grow and decrease in size.
>
> Joe

##########

Hi Joe,
thank for the suggestion, but this is rather complicated, compared to
using the config-VIs. But Rob showed a way to get this things working, in
the news posting below.

Bye,
Rainer

[Rob Cole]

One method that I have used is to make a VI that contains all of the variables that you wish to save (an actual global does not work). Open a reference to that VI and you can read/write to the variables. When you are done, use the Invoke node to "Make Current Values Default" and then another Invoke to "Save VI". These VIs can actually be saved in an LLB.

Rob

[Rainer Ehrt]

Rob Cole wrote:

> One method that I have used is to make a VI that contains all of the
> variables that you wish to save (an actual global does not work). Open
> a reference to that VI and you can read/write to the variables. When
> you are done, use the Invoke node to "Make Current Values Default" and
> then another Invoke to "Save VI". These VIs can actually be saved in
> an LLB.
>
> Rob

############

Hi Rob,
this sounds very good and seems not to be more complicated than using the
regular config- VIs. And its advantage is that the config data isn't saved
in clear-text, so the user can't edit it wheather its located separate or
in a LLB.
I'm going to try it out.

Thanks,
Rainer