Released 7. sept 1999 by Informatics
|This Delphi component is freeware, but please do not modify the source; contact
us so we can make the changes instead.
TinfRegistry makes it easier for you to interface the Windows registry. It offers methods for exporting, importing and compare registry files. It also provide very easy-to-use methods to read and write directly from/to registry. Try it !
NB! If you use D4 install IORegistry.pas, and if you use D3 install IORegistryD3.pas.
|Author||Informatics, Morten Høyseth|
overloaded method ExportRegistry to export from registry.
Use overloaded method DoImport to import to registry
Use overloaded method GetRegistryValue to retrieve data from reg.
Use overloaded method SetRegistryValue to set data to reg. from file.
Use CompareRegFiles to compare two registry files
NB! CompareRegFiles is veeeery slow on files larger than 500kb, do not even think of use it on files larger than that. Use it on portions of the registry only. A faster version will be implemented in the next version, this one is stringlist based and pretty slow. We just needed the function immediatly, so it is far, far from optimized.
|NewKeyList||TStringList. Used when comparing two registry files. The keys that are added (in the new reg file) are stored in this property, with key and data. No default.|
|DeletedKeyList||TStringList. Used when comparing two registry files. The keys that are deleted (in the new reg file) are stored in this property, with key and data. No default.|
|ExistingKeyList||TStringList. Used when comparing two registry files. The keys that exists in both files, but with different underlaying data, is stored here. No default.|
|RegHeader||String. The header in the registry file. Default if REGEDIT4. Used when making f.ex. export registry files.|
|DataNameValueDelim||Char. The delimiter between the dataname and value in a registry file. Default is =.|
|StringStartEndChar||Char. If the datavalue is a string, this property encapsulates the string value. Default is ".|
|RootStart||Char. The start character of the key in a registry file, the RootStart and RootEnd encapsulates the key. Default is [.|
|RootEnd||Char. The end character of the key in a registry file, the RootStart and RootEnd encapsulates the key. Default is ].|
|Filename||String. If you choose not to pass the filename as a parameter, you could set the filename to this property. Used when importing from - and exporting to a file. ean. Include subkeys when exporting. Default is true.|
|KeyToGet||String.Specify the key you want to export. F.ex. SOFTWARE\Microsoft\Java VM\Security. No default.|
|ExportDestination||TExpImpSource. Specifies if you want the export result stored in a file or a property. Default is eiFile.|
|ImportSource||TExpImpSource. Specifies if you want to import from a file or a property. Default is eiFile.|
|RegistryData||TStringList. If you choose to import or export from/to property (ExportDestionation or ImportSource set to eiProperty), this is the property export will export to or import will import from. No default.|
when the progress changes, when comparing two registry files.
Progress, MaxProgress, Level and maxlevel is easy to retrieve from this procedure, they are passed as parameters
Explaination of level and progress:
The process of comparing two registry files is divided in levels, each level has its own progress. Each level is finished before starting at the next. F.ex. the first level can be sorting out new keys with data, the next sorting out deleted keys with data, a third comparing existing keys datavalues.The natural thing, if you use progressbars, would be to use two meters. One for the total progress (levels), and one for the progress on the current level.
|v0.7 10.06.99 - only export implemented
v1.0 16.06.99 - both import and export seem to work fine
v1.1 16.08.99 - get/set methods for registry read/write added
v1.2 17.08.99 - export/import to property made possible
v1.3 01.09.99 - comparing two regfiles function added
v1.4 06.09.99 - progress variables added, use when comparing reg-files
v1.4.1 07.09.99 - small code cleanup
|1. File information part
a. uses declarations
b. const declarations
c. type declarations
d. var declarations
a. Manually gen. procedure & function implementations (level 1.0)
b. Automatically gen. procedure & function implementations (level 2.0)
c. Registration, initialization & finalization (level 3.0)
email@example.com or firstname.lastname@example.org
|© copyright 1999 Informatics|