TStorageLocation Class Reference

Defines valid storage locations for component list import, export and delete operations. More...

Static Public Attributes
static final int	slFile = acquireJNI.slFile_get()
	Stores/loads the setting in/from an XML file.
static final int	slNative = acquireJNI.slNative_get()
	Stores/loads the setting in/from a platform dependent location.
static final int	slNative_Raw = acquireJNI.slNative_Raw_get()
	Stores/loads the setting in/from a platform dependent location.
static final int	slRAM = acquireJNI.slRAM_get()
	Stores/loads the setting in/from RAM file.

Detailed Description

Defines valid storage locations for component list import, export and delete operations.

Component lists can be imported and exported from/to XML files, process RAM and (under Windows©) from/into the Registry.

Since

2.19.0

Member Data Documentation

slFile

final int slFile = acquireJNI.slFile_get()

static

Stores/loads the setting in/from an XML file.

Setting data will be imported/exported from/to an XML file.

slNative

final int slNative = acquireJNI.slNative_get()

static

Stores/loads the setting in/from a platform dependent location.

Under Windows© the Registry will be used to as a platform dependent location, while under other platforms an XML file will be processed in the path specified as the settings name.

Note

Please note, that using this mode will introduce platform dependency. E.g. specifying this mode under Linux will process XML data, while under Windows© the Registry will be used. This is why A call to a load function with this mode with the corresponding XML file in the applications directory might succeed under Linux while it fails under Windows©.

slNative_Raw

final int slNative_Raw = acquireJNI.slNative_Raw_get()

static

Stores/loads the setting in/from a platform dependent location.

Under Windows© the Registry will be used to as a platform dependent location, while under other platforms an XML file will be processed in the path specified as the settings name.

Note

Please note, that using this mode will introduce platform dependency. E.g. specifying this mode under Linux will process XML data, while under Windows© the Registry will be used. This is why A call to a load function with this mode with the corresponding XML file in the applications directory might succeed under Linux while it fails under Windows©.

Under Windows© with this mode an arbitrary hive from the registry can be used to create a tree of lists and properties. This only makes sense for very special applications and therefore is not needed to write applications, that load and store current settings.

slRAM

final int slRAM = acquireJNI.slRAM_get()

static

Stores/loads the setting in/from RAM file.

Setting data will be stored in the RAM of the current process. Data stored this way should be freed when no longer needed to avoid a waste of memory. However when shutting down Impact Acquire completely (e.g. when unloading the mvPropHandling library from memory all memory allocated by settings stored this way will be freed automatically).