- 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 implementations. For wxFileConfig, these styles
- determine whether a local or global config file is created or used: if
- wxCONFIG_USE_GLOBAL_FILE is used, then settings are read from the global
- config file and if wxCONFIG_USE_LOCAL_FILE is used, settings are read from
- and written to local config file (if they are both set, global file is read
- first, then local file, overwriting global settings). 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 wxRegConfig, thie GLOBAL flag refers to HKLM
- key while LOCAL one is for the usual HKCU one.
-
- 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.
-
- On non-VMS Unix systems, the default local configuration file is ~/.appname.
- However, this path may be also used as user data directory
- (see wxStandardPaths::GetUserDataDir) if
- the application has several data files. In this case wxCONFIG_USE_SUBDIR
- flag, which changes the default local configuration file to ~/.appname/appname
- should be used. Notice that this flag is ignored if localFilename is
- provided. This function is new since wxWidgets version 2.8.2
-
- 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:\mydir instead of the usual storage of
- foo=C:\\mydir.
-
- 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.
-
+ 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 implementations. For wxFileConfig, these styles
+ determine whether a local or global config file is created or used: if
+ wxCONFIG_USE_GLOBAL_FILE is used, then settings are read from the global
+ config file and if wxCONFIG_USE_LOCAL_FILE is used, settings are read from
+ and written to local config file (if they are both set, global file is read
+ first, then local file, overwriting global settings). 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 wxRegConfig, thie GLOBAL flag refers to HKLM
+ key while LOCAL one is for the usual HKCU one.
+ 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.
+ On non-VMS Unix systems, the default local configuration file is ~/.appname.
+ However, this path may be also used as user data directory
+ (see wxStandardPaths::GetUserDataDir) if
+ the application has several data files. In this case wxCONFIG_USE_SUBDIR
+ flag, which changes the default local configuration file to
+ ~/.appname/appname
+ should be used. Notice that this flag is ignored if localFilename is
+ provided. This function is new since wxWidgets version 2.8.2
+ 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:\mydir instead of the usual storage of
+ foo=C:\\mydir.
+ 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.