ContentSetDefaultParams: Difference between revisions
(Initial document version (copy & paste)) |
(Backlink and category) |
||
| Line 19: | Line 19: | ||
DefaultIniName Suggested location+name of the ini file where the plugin could store its data. This is a fully qualified path+file name, and will be in the same directory as the wincmd.ini. It's recommended to store the plugin data in this file or at least in this directory, because the plugin directory or the Windows directory may not be writable! | DefaultIniName Suggested location+name of the ini file where the plugin could store its data. This is a fully qualified path+file name, and will be in the same directory as the wincmd.ini. It's recommended to store the plugin data in this file or at least in this directory, because the plugin directory or the Windows directory may not be writable! | ||
{{backlink|Content plugins developer guide|Content plugins developer guide}} | |||
[[category:Content plugin API]] | |||
Latest revision as of 15:16, 15 April 2017
ContentDefaultParamStruct is passed to ContentSetDefaultParams to inform the plugin about the current plugin interface version and ini file location.
Declaration:
typedef struct { int size; DWORD PluginInterfaceVersionLow; DWORD PluginInterfaceVersionHi; char DefaultIniName[MAX_PATH]; } ContentDefaultParamStruct ;
Description of struct members:
size The size of the structure, in bytes. Later revisions of the plugin interface may add more structure members, and will adjust this size field accordingly.
PluginInterfaceVersionLow Low value of plugin interface version. This is the value after the comma, multiplied by 100! Example. For plugin interface version 1.30, the low DWORD is 30 and the high DWORD is 1.
PluginInterfaceVersionHi High value of plugin interface version.
DefaultIniName Suggested location+name of the ini file where the plugin could store its data. This is a fully qualified path+file name, and will be in the same directory as the wincmd.ini. It's recommended to store the plugin data in this file or at least in this directory, because the plugin directory or the Windows directory may not be writable!
Back to Content plugins developer guide