🚀 go-pugleaf

"Phuoc Can HUA" <home}a+t{huaonline.com> wrote in message
news:oprso8ohk2bq7az6@newsgroups.borland.com...
> Since I don't want to check each single entry I put
> all in one try{} and as soon as one fails then it goes
> to the block for default values.

That is not a very good design approach.  There are several different
reasons why a particular value may fail at any time, not all of them are
data failures.  You shouldn't need to force everything to defaults just
because one particular value fails for any number of reasons.

> The problem is whenever a new version has a new
> parameter then it will reset all the settings in the first run :-(

Then you will just have to test each value individually.  If you want an
elegant solution, then why not just wrap the reading in a method that
handles the details for you?  It can do the existence checking and default
value storing and such as appropriate.  For example:

    // assuming Reg is a TRegistry that is a member of the form
    // and is already opened to the target registry key

    int __fastcall TForm1::RegReadInteger(const AnsiString &Name, int
Default)
    {
        try
        {
            if( !Reg->ValueExists(Name) )
                Reg->WriteInteger(Name, Default);
            return Reg->ReadInteger(Name);
        }
        catch(Exception&) {}
        return Default;
    }

Then you can call the reading method whenever needed instead of performing
the Registry code directly:

    int i = RegReadInteger("Some Value", 10);

You can expand on this to include reading functions for strings, boolean,
etc. as well.


Gambit