3.3 - Runtime Settings

Table of Contents

• 3.3.1 Settings Directory Structure
• 3.3.2 Loading and Saving Settings

VR-Forces hashave various runtime settings, for example, enabling and disabling entity labels.

These settings are owned by Settings Managers. Settings at runtime are DtDeSettings objects, owned by the DtDeSettingsManager. They are saved into the ./appData/settings directory, and the factory defaults are in ./factory/settings.

3.3.1 Settings Directory Structure

The ./appData/settings directory is the root directory for user settings, and each application has its own subdirectory (for example, ./appData/settings/stealth and ./appData/settings/vantageIG). Similarly, ./factory/settings is the factory settings root directory, with subdirectories for each application. The settings directories are configured by the DtDePathConfiguration. When an application wants to load a default settings file, it should check the user settings directory first. If no appropriate file is found, the factory settings directory should be checked.

3.3.2 Loading and Saving Settings

Each DtDeSettings object is responsible for loading and saving itself. The settings objects can load and save from default files, factory files, or a specified file path. Please see DtDeSettings.h for detailed Toolkit documentation. You can get the DtDeSettings object for a particular group of settings from the DtDeSettingsManager, as follows:

DtDeSettings* settings = DtDeSettingsManager::instance(myDe).findSettings("Settings Name");

[<< The Event Loop] [Home] [Top of Page] [Records >>]