10-30-2019 05:24 AM
10-30-2019 06:03 AM
10-30-2019 06:16 AM
You don't save "files" in registry, you create subkey and values.
When you develop your own Soft, I think it only make sense to put data in the registry if you want other softs to be able to read/write some general config of you soft.
Accessing the registry often brings a lot of IT user restriction considerations, so if you don't really need it, just stay out of it ;).
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
10-30-2019 07:50 AM
Hi,
i
I'm trying to undrestand a LabVIEW program in which the developer create register and write value in register .
i don't undrestand the reason behind that ?
10-30-2019 07:58 AM
What kind of information / values are saved in the registry?
Do you have any idea if any other Software will use the key written by the application you are working on?
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
10-30-2019 08:03 AM
ID , years , month , hour
i don't know if the keys is going to be used by other software.
10-30-2019 08:17 AM
Well... if there is no obvious reason, apart from asking the original developer I don't think you will ever know.
Maybe he was scared that if he stored his data in files, someone might delete the files, maybe he though the registry was a "safer" place to avoid people deleting useful information... I'm just poking in the dark really.
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
10-30-2019 08:39 AM
Just to be sure we are talking about the same thing:
It is not uncommon for a Data Processing program to want to save "Configuration Settings" (like ID, and TimeStamp information) somewhere, especially if these settings are often re-used each time the program is run. An example of this are ".ini" files that have a Section/Key/Value hierarchy. NI has a set of functions in the File I/O Palette for such files.
The other place such data could be saved is in the Windows "Registry", a complex database that lies at the heart of the Windows Operating System, and accordingly is very dangerous for ordinary users to even look at, much less modify. One of the quickest ways to force a re-install of Windows is a careless Registry edit, hence I strongly advise against touching it.
Bob Schor
10-30-2019 09:56 AM
@Bob_Schor wrote:
Just to be sure we are talking about the same thing:
It is not uncommon for a Data Processing program to want to save "Configuration Settings" (like ID, and TimeStamp information) somewhere, especially if these settings are often re-used each time the program is run. An example of this are ".ini" files that have a Section/Key/Value hierarchy. NI has a set of functions in the File I/O Palette for such files.
The other place such data could be saved is in the Windows "Registry", a complex database that lies at the heart of the Windows Operating System, and accordingly is very dangerous for ordinary users to even look at, much less modify. One of the quickest ways to force a re-install of Windows is a careless Registry edit, hence I strongly advise against touching it.
Bob Schor
Amen to that.
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus