Appendix

Previous

Appendix


Registry/ini-file keys

The following registry or ini-file keys are used (including sample values):


[Window]

PosX=409

PosY=230

Width=391

Height=647

The Window settings define the location and the size of the dialog upon startup.


[Program]

Version=100

The Program settings store certain program related data. In this case, it is just the version of the program, which wrote the registry.


[Settings]

component=0

target_r=51

target_c=50pF

target_rn=7

maxerr_r=1%

maxerr_c=1 %

maxerr_rn=1 %

maxdev_r=10

maxdev_c=10

maxdev_rn=10

u2=3.2

imin=10mA

imax=20mA

iload=1mA

C_List=d:\Utilities\ParSer\MyCSet.csv

R_List=d:\Utilities\ParSer\MyRSet.csv

flags_r=0x706

flags_c=0xc706

flags_rn=0x8706

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.


History

V1.0

- Implemented private sets of components.

- The first version which is compiled with Microsoft Visual C++ 2010 Express.

- Using ResEdit (http://www.resedit.net/) to generate the resources.

- Using HelpNDoc to generate this Help File.


A number of pre-1.0 versions were distributed, but i missed to write a history list (though each version may be reconstructed from my CVS version management system). It doesn't seem worthwile to reconstruct a history list.


Development environment

I've used Open Watcom development tools in the past, which may be downloaded from http://www.openwatcom.org/.

Recently I changed to 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 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: Full featured Documentation generator