The following registry or ini-file keys are used (including sample values):
The Window settings define the location and the size of the dialog upon startup.
The Program settings store certain program related data. In this case, it is just the version of the program, which wrote the registry.
The Settings remeber the last parameters used by the program.
Using an ini file or the registry?
ParSer permits to use the windows registry or a dedicated ini-file to store configuration data. Which one shall be used?
Well, it's pretty much a matter of personal taste. Microsoft discurages the use of ini files, but quite a few people, including myself, prefer them over using the registry. The big advantages of an ini file are portability, the possibility to make backups and the possibility to use different configurations for different purposes. For backing up or porting ParSer and its configuration to a different computer, just copy the executable and the ini-file and you are done. Maybe some pathnames must be adapted, but that can be done easily with any text editor, as the ini file is a normal text file. Using an ini file may not be much of an advantage for a simple program like ParSer, but for a more complex program, it can save your day.
But again, it depends on your peronal taste, which one you use.
Both changes are not much of an advantage for ParSer, but I changed the "winlib" accordingly and so these changes came for free. Unicode may be used in the files for private resistor and capacitor sets. That applies to the filename and to the comment lines. The 64-bit version came also practically for free, but it does not seem to have an advantage in execution speed or memory use. Both versions are included in the package. I suggest to use the one, which fits to your operating system.
A number of pre-1.0 versions were distributed, but i missed to write a history list.
Since a few years I use the free version of Microsoft Visual C++ Express (http://www.microsoft.com/visualstudio/en-us/products/2010-editions/express). It generates faster and more compact code than Open Watcom (which I used earlier) and it is better supported by 3rd party tools like ResEdit (http://www.resedit.net/).
This document was generated with HelpNDoc (http://www.helpndoc.com/).
Contacting the author
I may be contacted by email at michael_@_dk8pp.de (remove the underscores; as I occasionally change my email addresses due to excessive spam, please check http://www.dk8pp.de if the above one should not work.)
Feel free to write an email if you find any problems or to suggest improvements.
Created with the Personal Edition of HelpNDoc: Easily create iPhone documentation