SettingStore

Introduction

Most of Omea-global settings are stored in the Omea SettingStore in the Section – Key – Value fashion. While some of them reflect the user-editable options, as found in the Tools -> Options dialog, or persist the window sizes, others control the way Omea behaves, formats, displays, and so on, and may not have an editing UI that allows to change them directly. This page lists some of those settings and tells you how you can change them to gain advanced control over the Omea application.

A Section denotes a group of settings that have similar purpose or are applicable to the same context. For example, the "NewspaperView()" section contains options that apply to the newspaper behavior, and "Clippings" controls the creation and behavior of the clippings.

A Key is a name of a particular setting in a Section, and Value is its value. Each Section is a collection of unique keys, and there cannot be two keys with the same name in one section. Each Key has a type (string, integer, boolean, etc), which means that all the valid values for this key must be of this type.

Most of the settings apply to both Omea Reader and Omea Pro. If not, there should be a note in the description of such a setting.

How to Change the Settings

Warning! Take care editing the Omea options! Setting them to incorrect values may cause Omea to function incorrectly, degrade the performance, or even impose your computer to a security risk. Be sure you know what you're doing.

The SettingStore is persisted in a form of a standard INI-file named "OmniaMea.ini". This file can be found in the Omea Database folder, as specified at Tools -> Options -> Paths -> Database Path. If you cannot run Omea, check the HKEY_CURRENT_USER\Software\JetBrains\Omea\DbPath Registry value for Omea Pro, and HKEY_CURRENT_USER\Software\JetBrains\Omea Reader\DbPath for Omea Reader. By default, it points to the %%LOCALAPPDATA%%\JetBrains\Omea folder (for example, c:\Documents and Settings\Username\Local Settings\Application Data\JetBrains\Omea).

Each section starts with the section header, and all the key-value pairs that follow it, up to the next section header or file end, belong to this section. Each key-value pair occupies a single line, and a key is separated from its value with an equality sign (=). Empty lines are ignored.

String values are not enclosed in quotes. Integer values, be they positive or negative, are written "as is". Boolean values are coerced to integers, where a zero value, 0, in the INI file means False, while any nonzero value, preferrably 1, means True.

[MySection]
StringValue=Internet Explorer
IntegerValue=5
NegInt=-5
BooleanTrue=1
BooleanFalse=0

[AnotherSection]
One=1
Two=2
Thee=3

Many=Infinite

Legend

The default table template is:

Flag values are:

• I = Internal (cannot be changed explicitly from the UI)
• D = Debug (introduced for debug purposes, usually combined with I)
• H = Hack (option provided for better control over some fine tuning parameter, that cannot be edited from the UI, and it's not quite sensitive to the application whether it's an option or a hard-coded value). Incapsulates the I flag. | <Description and Comments>

Settings

Note As a safety measure, some of the potentionaly dangerous settings have been excluded from the public spec. They can be found in an internal Omea space, on the [Debug Setting Store] page.

General Section

Clippings Section

ResourceEditWindow Section

Formatting Section

Newspaper Sections Family

"Newspaper()" - the common newspaper section

"Newspaper(…)" - resource-types-dependent section

Here and below the ellipsis (…) stands for a lexicographically-ordered comma-separated list of string representations of resource types displayed by this newspaper, eg "Newspaper(Fragment,RSSItem)".
Note that this also applies to the case when there are no resources to be displayed and thus no resource types, in which case the common section (see above) is used.

Search Bar