Retrieves an integer associated with a key in the specified section of an initialization file.
UINT GetPrivateProfileInt( LPCTSTR lpAppName, LPCTSTR lpKeyName, INT nDefault, LPCTSTR lpFileName );
The name of the section in the initialization file.
The name of the key whose value is to be retrieved. This value is in the form of a string; the GetPrivateProfileInt function converts the string into an integer and returns the integer.
The default value to return if the key name cannot be found in the initialization file.
The name of the initialization file. If this parameter does not contain a full path to the file, the system searches for the file in the Windows directory.
The return value is the integer equivalent of the string following the specified key name in the specified initialization file. If the key is not found, the return value is the specified default value.
The function searches the file for a key that matches the name specified by the lpKeyName parameter under the section name specified by the lpAppName parameter. A section in the initialization file must have the following form:
[section] key=value . . .
The GetPrivateProfileInt function is not case-sensitive; the strings in lpAppName and lpKeyName can be a combination of uppercase and lowercase letters.
An application can use the GetProfileInt function to retrieve an integer value from the Win.ini file.
The system maps most .ini file references to the registry, using the mapping defined under the following registry key:HKEY_LOCAL_MACHINE<b>SOFTWARE<b>Microsoft<b>Windows NT<b>CurrentVersion<b>IniFileMapping
This mapping is likely if an application modifies system-component initialization files, such as Control.ini, System.ini, and Winfile.ini. In these cases, the function retrieves information from the registry, not from the initialization file; the change in the storage location has no effect on the function's behavior.
The profile functions use the following steps to locate initialization information:
- Look in the registry for the name of the initialization file under the IniFileMapping key.
- Look for the section name specified by lpAppName. This will be a named value under the key that has the name of the initialization file, or a subkey with this name, or the name will not exist as either a value or subkey.
- If the section name specified by lpAppName is a named value, then that value specifies where in the registry you will find the keys for the section.
- If the section name specified by lpAppName is a subkey, then named values under that subkey specify where in the registry you will find the keys for the section. If the key you are looking for does not exist as a named value, then there will be an unnamed value (shown as <No Name>) that specifies the default location in the registry where you will find the key.
- If the section name specified by lpAppName does not exist as a named value or as a subkey, then there will be an unnamed value (shown as <No Name>) that specifies the default location in the registry where you will find the keys for the section.
- If there is no subkey or entry for the section name, then look for the actual initialization file on the disk and read its contents.
- ! - this character forces all writes to go both to the registry and to the .ini file on disk.
- # - this character causes the registry value to be set to the value in the Windows 3.1 .ini file when a new user logs in for the first time after setup.
- @ - this character prevents any reads from going to the .ini file on disk if the requested data is not found in the registry.
- USR: - this prefix stands for HKEY_CURRENT_USER, and the text after the prefix is relative to that key.
- SYS: - this prefix stands for HKEY_LOCAL_MACHINE\SOFTWARE, and the text after the prefix is relative to that key.
|Windows version||Windows 2000 Professional [desktop apps only] Windows 2000 Server [desktop apps only]|
|Header||winbase.h (include Windows.h)|