wxConfigBase

wxConfigBase class defines the basic interface of all config classes. It can not be used by itself (it is an abstract base class) and you will always use one of its derivations: wxFileConfig, wxRegConfig or any other.

However, usually you don't even need to know the precise nature of the class you're working with but you would just use the wxConfigBase methods. This allows you to write the same code regardless of whether you're working with the registry under Win32 or text-based config files under Unix (or even Windows 3.1 .INI files if you're really unlucky). To make writing the portable code even easier, wxWidgets provides a typedef wxConfig which is mapped onto the native wxConfigBase implementation on the given platform: i.e. wxRegConfig under Win32 and wxFileConfig otherwise.

See config overview for the descriptions of all features of this class.

It is highly recommended to use static functions Get() and/or Set(), so please have a look at them.

Derived from

No base class

Include files

<wx/config.h> (to let wxWidgets choose a wxConfig class for your platform)
<wx/confbase.h> (base config class)
<wx/fileconf.h> (wxFileConfig class)
<wx/msw/regconf.h> (wxRegConfig class)

Example

Here is how you would typically use this class:

  // using wxConfig instead of writing wxFileConfig or wxRegConfig enhances
  // portability of the code
  wxConfig *config = new wxConfig("MyAppName");

  wxString str;
  if ( config->Read("LastPrompt", &str) ) {
    // last prompt was found in the config file/registry and its value is now
    // in str
    ...
  }
  else {
    // no last prompt...
  }

  // another example: using default values and the full path instead of just
  // key name: if the key is not found , the value 17 is returned
  long value = config->Read("/LastRun/CalculatedValues/MaxValue", 17);
  ...
  ...
  ...
  // at the end of the program we would save everything back
  config->Write("LastPrompt", str);
  config->Write("/LastRun/CalculatedValues/MaxValue", value);

  // the changes will be written back automatically
  delete config;

This basic example, of course, doesn't show all wxConfig features, such as enumerating, testing for existence and deleting the entries and groups of entries in the config file, its abilities to automatically store the default values or expand the environment variables on the fly. However, the main idea is that using this class is easy and that it should normally do what you expect it to.

NB: in the documentation of this class, the words "config file" also mean "registry hive" for wxRegConfig and, generally speaking, might mean any physical storage where a wxConfigBase-derived class stores its data.



Static functions

These functions deal with the "default" config object. Although its usage is not at all mandatory it may be convenient to use a global config object instead of creating and deleting the local config objects each time you need one (especially because creating a wxFileConfig object might be a time consuming operation). In this case, you may create this global config object in the very start of the program and Set() it as the default. Then, from anywhere in your program, you may access it using the Get() function. Note that you must delete this object (usually in wxApp::OnExit) in order to avoid memory leaks, wxWidgets won't do it automatically.

As it happens, you may even further simplify the procedure described above: you may forget about calling Set(). When Get() is called and there is no current object, it will create one using Create() function. To disable this behaviour DontCreateOnDemand() is provided.

Note: You should use either Set() or Get() because wxWidgets library itself would take advantage of it and could save various information in it. For example wxFontMapper or Unix version of wxFileDialog have the ability to use wxConfig class.

Set
Get
Create
DontCreateOnDemand



Constructor and destructor

wxConfigBase
~wxConfigBase



Path management

As explained in config overview, the config classes support a file system-like hierarchy of keys (files) and groups (directories). As in the file system case, to specify a key in the config class you must use a path to it. Config classes also support the notion of the current group, which makes it possible to use the relative paths. To clarify all this, here is an example (it is only for the sake of demonstration, it doesn't do anything sensible!):

  wxConfig *config = new wxConfig("FooBarApp");

  // right now the current path is '/'
  conf->Write("RootEntry", 1);

  // go to some other place: if the group(s) don't exist, they will be created
  conf->SetPath("/Group/Subgroup");

  // create an entry in subgroup
  conf->Write("SubgroupEntry", 3);

  // '..' is understood
  conf->Write("../GroupEntry", 2);
  conf->SetPath("..");

  wxASSERT( conf->Read("Subgroup/SubgroupEntry", 0l) == 3 );

  // use absolute path: it is allowed, too
  wxASSERT( conf->Read("/RootEntry", 0l) == 1 );

Warning: it is probably a good idea to always restore the path to its old value on function exit:

  void foo(wxConfigBase *config)
  {
    wxString strOldPath = config->GetPath();

    config->SetPath("/Foo/Data");
    ...

    config->SetPath(strOldPath);
  }

because otherwise the assert in the following example will surely fail (we suppose here that foo() function is the same as above except that it doesn't save and restore the path):

  void bar(wxConfigBase *config)
  {
    config->Write("Test", 17);

    foo(config);

    // we're reading "/Foo/Data/Test" here! -1 will probably be returned...
    wxASSERT( config->Read("Test", -1) == 17 );
  }

Finally, the path separator in wxConfigBase and derived classes is always '/', regardless of the platform (i.e. it is not ' $\backslash\backslash$' under Windows).

SetPath
GetPath



Enumeration

The functions in this section allow to enumerate all entries and groups in the config file. All functions here return FALSEwhen there are no more items.

You must pass the same index to GetNext and GetFirst (don't modify it). Please note that it is not the index of the current item (you will have some great surprises with wxRegConfig if you assume this) and you shouldn't even look at it: it is just a "cookie" which stores the state of the enumeration. It can't be stored inside the class because it would prevent you from running several enumerations simultaneously, that's why you must pass it explicitly.

Having said all this, enumerating the config entries/groups is very simple:

  wxConfigBase *config = ...;
  wxArrayString aNames;

  // enumeration variables
  wxString str;
  long dummy;

  // first enum all entries
  bool bCont = config->GetFirstEntry(str, dummy);
  while ( bCont ) {
    aNames.Add(str);

    bCont = GetConfig()->GetNextEntry(str, dummy);
  }

  ... we have all entry names in aNames...

  // now all groups...
  bCont = GetConfig()->GetFirstGroup(str, dummy);
  while ( bCont ) {
    aNames.Add(str);

    bCont = GetConfig()->GetNextGroup(str, dummy);
  }

  ... we have all group (and entry) names in aNames...

There are also functions to get the number of entries/subgroups without actually enumerating them, but you will probably never need them.

GetFirstGroup
GetNextGroup
GetFirstEntry
GetNextEntry
GetNumberOfEntries
GetNumberOfGroups



Tests of existence

HasGroup
HasEntry
Exists
GetEntryType



Miscellaneous functions

GetAppName
GetVendorName
SetUmask



Key access

These function are the core of wxConfigBase class: they allow you to read and write config file data. All Read function take a default value which will be returned if the specified key is not found in the config file.

Currently, only two types of data are supported: string and long (but it might change in the near future). To work with other types: for int or bool you can work with function taking/returning long and just use the casts. Better yet, just use long for all variables which you're going to save in the config file: chances are that sizeof(bool) == sizeof(int) == sizeof(long) anyhow on your system. For float, double and, in general, any other type you'd have to translate them to/from string representation and use string functions.

Try not to read long values into string variables and vice versa: although it just might work with wxFileConfig, you will get a system error with wxRegConfig because in the Windows registry the different types of entries are indeed used.

Final remark: the szKey parameter for all these functions can contain an arbitrary path (either relative or absolute), not just the key name.

Read
Write
Flush



Rename entries/groups

The functions in this section allow to rename entries or subgroups of the current group. They will return FALSEon error. typically because either the entry/group with the original name doesn't exist, because the entry/group with the new name already exists or because the function is not supported in this wxConfig implementation.

RenameEntry
RenameGroup



Delete entries/groups

The functions in this section delete entries and/or groups of entries from the config file. DeleteAll() is especially useful if you want to erase all traces of your program presence: for example, when you uninstall it.

DeleteEntry
DeleteGroup
DeleteAll



Options

Some aspects of wxConfigBase behaviour can be changed during run-time. The first of them is the expansion of environment variables in the string values read from the config file: for example, if you have the following in your config file:

  # config file for my program
  UserData = $HOME/data

  # the following syntax is valud only under Windows
  UserData = %windir%\\data.dat
the call to config->Read("UserData") will return something like "/home/zeitlin/data" if you're lucky enough to run a Linux system ;-)

Although this feature is very useful, it may be annoying if you read a value which containts '$' or '%' symbols (% is used for environment variables expansion under Windows) which are not used for environment variable expansion. In this situation you may call SetExpandEnvVars(false) just before reading this value and SetExpandEnvVars(true) just after. Another solution would be to prefix the offending symbols with a backslash.

The following functions control this option:

IsExpandingEnvVars
SetExpandEnvVars
SetRecordDefaults
IsRecordingDefaults



wxConfigBase::wxConfigBase



wxConfigBase(const wxString& appName = wxEmptyString, const wxString& vendorName = wxEmptyString, const wxString& localFilename = wxEmptyString, const wxString& globalFilename = wxEmptyString, long style = 0, wxMBConv& conv = wxConvUTF8)

This is the default and only constructor of the wxConfigBase class, and derived classes.

Parameters

appName
The application name. If this is empty, the class will normally use wxApp::GetAppName to set it. The application name is used in the registry key on Windows, and can be used to deduce the local filename parameter if that is missing.

vendorName
The vendor name. If this is empty, it is assumed that no vendor name is wanted, if this is optional for the current config class. The vendor name is appended to the application name for wxRegConfig.

localFilename
Some config classes require a local filename. If this is not present, but required, the application name will be used instead.

globalFilename
Some config classes require a global filename. If this is not present, but required, the application name will be used instead.

style
Can be one of wxCONFIG_USE_LOCAL_FILE and wxCONFIG_USE_GLOBAL_FILE. The style interpretation depends on the config class and is ignored by some. For wxFileConfig, these styles determine whether a local or global config file is created or used. If the flag is present but the parameter is empty, the parameter will be set to a default. If the parameter is present but the style flag not, the relevant flag will be added to the style. For wxFileConfig you can also add wxCONFIG_USE_RELATIVE_PATH by logically or'ing it to either of the _FILE options to tell wxFileConfig to use relative instead of absolute paths. For wxFileConfig, you can also add wxCONFIG_USE_NO_ESCAPE_CHARACTERS which will turn off character escaping for the values of entries stored in the config file: for example a foo key with some backslash characters will be stored as foo=C:$\backslash$mydir instead of the usual storage of foo=C: $\backslash\backslash$mydir. For wxRegConfig, this flag refers to HKLM, and provides read-only access.

The wxCONFIG_USE_NO_ESCAPE_CHARACTERS style can be helpful if your config file must be read or written to by a non-wxWidgets program (which might not understand the escape characters). Note, however, that if wxCONFIG_USE_NO_ESCAPE_CHARACTERS style is used, it is is now your application's responsibility to ensure that there is no newline or other illegal characters in a value, before writing that value to the file.

conv
This parameter is only used by wxFileConfig when compiled in Unicode mode. It specifies the encoding in which the configuration file is written.

Remarks

By default, environment variable expansion is on and recording defaults is off.



wxConfigBase::~wxConfigBase



~wxConfigBase(void)

Empty but ensures that dtor of all derived classes is virtual.



wxConfigBase::Create



static wxConfigBase * Create(void)

Create a new config object: this function will create the "best" implementation of wxConfig available for the current platform, see comments near the definition of wxCONFIG_WIN32_NATIVE for details. It returns the created object and also sets it as the current one.



wxConfigBase::DontCreateOnDemand



void DontCreateOnDemand(void)

Calling this function will prevent Get() from automatically creating a new config object if the current one is NULL. It might be useful to call it near the program end to prevent "accidental" creation of a new config object.



wxConfigBase::DeleteAll



bool DeleteAll(void)

Delete the whole underlying object (disk file, registry key, ...). Primarly for use by uninstallation routine.



wxConfigBase::DeleteEntry



bool DeleteEntry(const wxString& key, bool bDeleteGroupIfEmpty = true)

Deletes the specified entry and the group it belongs to if it was the last key in it and the second parameter is true.



wxConfigBase::DeleteGroup



bool DeleteGroup(const wxString& key)

Delete the group (with all subgroups)



wxConfigBase::Exists

bool Exists(wxString& strName) const

returns TRUEif either a group or an entry with a given name exists



wxConfigBase::Flush



bool Flush(bool bCurrentOnly = false)

permanently writes all changes (otherwise, they're only written from object's destructor)



wxConfigBase::Get



static wxConfigBase * Get(bool CreateOnDemand = true)

Get the current config object. If there is no current object and CreateOnDemand is true, creates one (using Create) unless DontCreateOnDemand was called previously.



wxConfigBase::GetAppName

wxString GetAppName(void) const

Returns the application name.



wxConfigBase::GetEntryType

enum wxConfigBase::EntryType GetEntryType(const wxString& name) const

Returns the type of the given entry or Unknown if the entry doesn't exist. This function should be used to decide which version of Read() should be used because some of wxConfig implementations will complain about type mismatch otherwise: e.g., an attempt to read a string value from an integer key with wxRegConfig will fail.

The result is an element of enum EntryType:

  enum EntryType
  {
    Type_Unknown,
    Type_String,
    Type_Boolean,
    Type_Integer,
    Type_Float
  };



wxConfigBase::GetFirstGroup

bool GetFirstGroup(wxString& str, long& index) const

Gets the first group.

wxPython での注意点: The wxPython version of this method returns a 3-tuple consisting of the continue flag, the value string, and the index for the next call.

wxPerl での注意点: In wxPerl this method takes no arguments and returns a 3-element list ( continue, str, index ).



wxConfigBase::GetFirstEntry

bool GetFirstEntry(wxString& str, long& index) const

Gets the first entry.

wxPython での注意点: The wxPython version of this method returns a 3-tuple consisting of the continue flag, the value string, and the index for the next call.

wxPerl での注意点: In wxPerl this method takes no arguments and returns a 3-element list ( continue, str, index ).



wxConfigBase::GetNextGroup

bool GetNextGroup(wxString& str, long& index) const

Gets the next group.

wxPython での注意点: The wxPython version of this method returns a 3-tuple consisting of the continue flag, the value string, and the index for the next call.

wxPerl での注意点: In wxPerl this method only takes the index parameter and returns a 3-element list ( continue, str, index ).



wxConfigBase::GetNextEntry

bool GetNextEntry(wxString& str, long& index) const

Gets the next entry.

wxPython での注意点: The wxPython version of this method returns a 3-tuple consisting of the continue flag, the value string, and the index for the next call.

wxPerl での注意点: In wxPerl this method only takes the index parameter and returns a 3-element list ( continue, str, index ).



wxConfigBase::GetNumberOfEntries

uint GetNumberOfEntries(bool bRecursive = false) const



wxConfigBase::GetNumberOfGroups

uint GetNumberOfGroups(bool bRecursive = false) const

Get number of entries/subgroups in the current group, with or without its subgroups.



wxConfigBase::GetPath

const wxString& GetPath(void) const

Retrieve the current path (always as absolute path).



wxConfigBase::GetVendorName

wxString GetVendorName(void) const

Returns the vendor name.



wxConfigBase::HasEntry

bool HasEntry(wxString& strName) const

returns TRUEif the entry by this name exists



wxConfigBase::HasGroup

bool HasGroup(const wxString& strName) const

returns TRUEif the group by this name exists



wxConfigBase::IsExpandingEnvVars

bool IsExpandingEnvVars(void) const

Returns TRUEif we are expanding environment variables in key values.



wxConfigBase::IsRecordingDefaults

bool IsRecordingDefaults(void) const

Returns TRUEif we are writing defaults back to the config file.



wxConfigBase::Read

bool Read(const wxString& key, wxString* str) const

Read a string from the key, returning TRUEif the value was read. If the key was not found, str is not changed.

bool Read(const wxString& key, wxString* str, const wxString& defaultVal) const

Read a string from the key. The default value is returned if the key was not found.

Returns TRUEif value was really read, FALSEif the default was used.

wxString Read(const wxString& key, const wxString& defaultVal) const

Another version of Read(), returning the string value directly.

bool Read(const wxString& key, long* l) const

Reads a long value, returning TRUEif the value was found. If the value was not found, l is not changed.

bool Read(const wxString& key, long* l, long defaultVal) const

Reads a long value, returning TRUEif the value was found. If the value was not found, defaultVal is used instead.

long Read(const wxString& key, long defaultVal) const

Reads a long value from the key and returns it. defaultVal is returned if the key is not found.

NB: writing

    conf->Read("key", 0);

won't work because the call is ambiguous: compiler can not choose between two Read functions. Instead, write:

    conf->Read("key", 0l);

bool Read(const wxString& key, double* d) const

Reads a double value, returning TRUEif the value was found. If the value was not found, d is not changed.

bool Read(const wxString& key, double* d, double defaultVal) const

Reads a double value, returning TRUEif the value was found. If the value was not found, defaultVal is used instead.

bool Read(const wxString& key, bool* b) const

Reads a bool value, returning TRUEif the value was found. If the value was not found, b is not changed.

bool Read(const wxString& key, bool* d, bool defaultVal) const

Reads a bool value, returning TRUEif the value was found. If the value was not found, defaultVal is used instead.

wxPython での注意点: In place of a single overloaded method name, wxPython implements the following methods:

2cm
Read(key, default="") Returns a string.
ReadInt(key, default=0) Returns an int.
ReadFloat(key, default=0.0) Returns a floating point number.

wxPerl での注意点: In place of a single overloaded method, wxPerl uses:

2cm
Read(key, default="") Returns a string
ReadInt(key, default=0) Returns an integer
ReadFloat(key, default=0.0) Returns a floating point number
ReadBool(key, default=0) Returns a boolean



wxConfigBase::RenameEntry



bool RenameEntry(const wxString& oldName, const wxString& newName)

Renames an entry in the current group. The entries names (both the old and the new one) shouldn't contain backslashes, i.e. only simple names and not arbitrary paths are accepted by this function.

Returns FALSEif oldName doesn't exist or if newName already exists.



wxConfigBase::RenameGroup



bool RenameGroup(const wxString& oldName, const wxString& newName)

Renames a subgroup of the current group. The subgroup names (both the old and the new one) shouldn't contain backslashes, i.e. only simple names and not arbitrary paths are accepted by this function.

Returns FALSEif oldName doesn't exist or if newName already exists.



wxConfigBase::Set



static wxConfigBase * Set(wxConfigBase * pConfig)

Sets the config object as the current one, returns the pointer to the previous current object (both the parameter and returned value may be NULL)



wxConfigBase::SetExpandEnvVars



void SetExpandEnvVars (bool bDoIt = true)

Determine whether we wish to expand environment variables in key values.



wxConfigBase::SetPath



void SetPath(const wxString& strPath)

Set current path: if the first character is '/', it is the absolute path, otherwise it is a relative path. '..' is supported. If strPath doesn't exist it is created.



wxConfigBase::SetRecordDefaults



void SetRecordDefaults(bool bDoIt = true)

Sets whether defaults are recorded to the config file whenever an attempt to read the value which is not present in it is done.

If on (default is off) all default values for the settings used by the program are written back to the config file. This allows the user to see what config options may be changed and is probably useful only for wxFileConfig.



wxConfigBase::Write



bool Write(const wxString& key, const wxString& value)



bool Write(const wxString& key, long value)



bool Write(const wxString& key, double value)



bool Write(const wxString& key, bool value)

These functions write the specified value to the config file and return TRUEon success.

wxPython での注意点: In place of a single overloaded method name, wxPython implements the following methods:

2cm
Write(key, value) Writes a string.
WriteInt(key, value) Writes an int.
WriteFloat(key, value) Writes a floating point number.

wxPerl での注意点: In place of a single overloaded method, wxPerl uses:

2cm
Write(key, value) Writes a string
WriteInt(key, value) Writes an integer
WriteFloat(key, value) Writes a floating point number
WriteBool(key, value) Writes a boolean

ymasuda 平成17年11月19日