<gconfentryfile>
<entrylist base="/schemas/apps/metacity/general">
<entry>
<key>action_double_click_titlebar</key>
<value>
<schema>
<owner>metacity</owner>
<type>string</type>
<locale name="C">
<default_value>
<value>
<string>toggle_maximize</string>
</value>
</default_value>
<short>Action on title bar double-click</short>
<long>
This option determines the effects of double-clicking on the
title bar. Current valid options are 'toggle_shade', which will
shade/unshade the window, 'toggle_maximize' which will
maximize/unmaximize the window, 'minimize' which will minimize
the window, and 'none' which will not do anything.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>application_based</key>
<value>
<schema>
<owner>metacity</owner>
<type>bool</type>
<locale name="C">
<default_value>
<value>
<bool>false</bool>
</value>
</default_value>
<short>(Not implemented) Navigation works in terms of applications not windows</short>
<long>
If true, then Metacity works in terms of applications rather than
windows. The concept is a bit abstract, but in general an
application-based setup is more like the Mac and less like
Windows. When you focus a window in application-based mode, all
the windows in the application will be raised. Also, in
application-based mode, focus clicks are not passed through to
windows in other applications. Application-based mode is,
however, largely unimplemented at the moment.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>audible_bell</key>
<value>
<schema>
<owner>metacity</owner>
<type>bool</type>
<locale name="C">
<default_value>
<value>
<bool>true</bool>
</value>
</default_value>
<short>System Bell is Audible</short>
<long>
Determines whether applications or the system can generate
audible 'beeps'; may be used in conjunction with 'visual bell' to
allow silent 'beeps'.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>auto_raise</key>
<value>
<schema>
<owner>metacity</owner>
<type>bool</type>
<locale name="C">
<default_value>
<value>
<bool>false</bool>
</value>
</default_value>
<short>Automatically raises the focused window</short>
<long>
If set to true, and the focus mode is either "sloppy" or "mouse"
then the focused window will be automatically raised after a
delay specified by the auto_raise_delay key. This is not related
to clicking on a window to raise it, nor to entering a window
during drag-and-drop.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>auto_raise_delay</key>
<value>
<schema>
<owner>metacity</owner>
<type>int</type>
<locale name="C">
<default_value>
<value>
<int>500</int>
</value>
</default_value>
<short>Delay in milliseconds for the auto raise option</short>
<long>
The time delay before raising a window if auto_raise is set to
true. The delay is given in thousandths of a second.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>button_layout</key>
<value>
<schema>
<owner>metacity</owner>
<type>string</type>
<locale name="C">
<default_value>
<value>
<string>menu:minimize,maximize,close</string>
</value>
</default_value>
<short>Arrangement of buttons on the titlebar</short>
<long>
Arrangement of buttons on the titlebar. The
value should be a string, such as
"menu:minimize,maximize,close"; the colon separates the
left corner of the window from the right corner, and
the button names are comma-separated. Duplicate buttons
are not allowed. Unknown button names are silently ignored
so that buttons can be added in future metacity versions
without breaking older versions.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>compositing_manager</key>
<value>
<schema>
<owner>metacity</owner>
<type>bool</type>
<locale name="C">
<default_value>
<value>
<bool>false</bool>
</value>
</default_value>
<short>Compositing Manager</short>
<long>
Determines whether Metacity is a compositing manager.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>disable_workarounds</key>
<value>
<schema>
<owner>metacity</owner>
<type>bool</type>
<locale name="C">
<default_value>
<value>
<bool>false</bool>
</value>
</default_value>
<short>Disable misfeatures that are required by old or broken applications</short>
<long>
Some applications disregard specifications in ways that result in
window manager misfeatures. This option puts Metacity in a
rigorously correct mode, which gives a more consistent user
interface, provided one does not need to run any misbehaving
applications.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>focus_mode</key>
<value>
<schema>
<owner>metacity</owner>
<type>string</type>
<locale name="C">
<default_value>
<value>
<string>click</string>
</value>
</default_value>
<short>Window focus mode</short>
<long>
The window focus mode indicates how windows are activated.
It has three possible values; "click" means windows must
be clicked in order to focus them, "sloppy" means windows
are focused when the mouse enters the window, and "mouse" means
windows are focused when the mouse enters the window and
unfocused when the mouse leaves the window.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>focus_new_windows</key>
<value>
<schema>
<owner>metacity</owner>
<type>string</type>
<locale name="C">
<default_value>
<value>
<string>smart</string>
</value>
</default_value>
<short>Control how new windows get focus</short>
<long>
This option provides additional control over how newly created
windows get focus. It has two possible values; "smart" applies
the user's normal focus mode, and "strict" results in windows
started from a terminal not being given focus.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>mouse_button_modifier</key>
<value>
<schema>
<owner>metacity</owner>
<type>string</type>
<locale name="C">
<default_value>
<value>
<string><Alt></string>
</value>
</default_value>
<short>Modifier to use for modified window click actions</short>
<long>
Clicking a window while holding down this modifier key
will move the window (left click), resize the window
(middle click), or show the window menu (right click).
Modifier is expressed as "<Alt>" or "<Super>"
for example.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>num_workspaces</key>
<value>
<schema>
<owner>metacity</owner>
<type>int</type>
<locale name="C">
<default_value>
<value>
<int>4</int>
</value>
</default_value>
<short>Number of workspaces</short>
<long>
Number of workspaces. Must be more than zero, and has a fixed
maximum to prevent making the desktop unusable by accidentally
asking for too many workspaces.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>raise_on_click</key>
<value>
<schema>
<owner>metacity</owner>
<type>bool</type>
<locale name="C">
<default_value>
<value>
<bool>true</bool>
</value>
</default_value>
<short>Whether raising should be a side-effect of other user interactions</short>
<long>
Many actions (e.g. clicking in the client area, moving or
resizing the window) normally raise the window as a
side-effect. Set this option to false to decouple raising from
other user actions. Even when this option is false, windows can
still be raised by an alt-left-click anywhere on the window, a
normal click on the window decorations, or by special messages,
such as activation requests from pagers. This option is
currently disabled in click-to-focus mode.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>reduced_resources</key>
<value>
<schema>
<owner>metacity</owner>
<type>bool</type>
<locale name="C">
<default_value>
<value>
<bool>false</bool>
</value>
</default_value>
<short>If true, trade off usability for less resource usage</short>
<long>
If true, metacity will give the user less feedback by using
wireframes, avoiding animations, or other means. This is a
significant reduction in usability for many users, but may allow
legacy applications to continue working, and may also be a
useful tradeoff for terminal servers. However, the wireframe
feature is disabled when accessibility is on.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>theme</key>
<value>
<schema>
<owner>metacity</owner>
<type>string</type>
<locale name="C">
<default_value>
<value>
<string>Clearlooks</string>
</value>
</default_value>
<short>Current theme</short>
<long>
The theme determines the appearance of window borders,
titlebar, and so forth.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>titlebar_font</key>
<value>
<schema>
<owner>metacity</owner>
<type>string</type>
<locale name="C">
<default_value>
<value>
<string>Sans Bold 10</string>
</value>
</default_value>
<short>Window title font</short>
<long>
A font description string describing a font for window
titlebars. The size from the description will only be used if the
titlebar_font_size option is set to 0. Also, this option is
disabled if the titlebar_uses_desktop_font option is set to true.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>titlebar_uses_system_font</key>
<value>
<schema>
<owner>metacity</owner>
<type>bool</type>
<locale name="C">
<default_value>
<value>
<bool>false</bool>
</value>
</default_value>
<short>Use standard system font in window titles</short>
<long>
If true, ignore the titlebar_font
option, and use the standard application font for window
titles.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>visual_bell</key>
<value>
<schema>
<owner>metacity</owner>
<type>bool</type>
<locale name="C">
<default_value>
<value>
<bool>false</bool>
</value>
</default_value>
<short>Enable Visual Bell</short>
<long>
Turns on a visual indication when an application or the system
issues a 'bell' or 'beep'; useful for the hard-of-hearing and for
use in noisy environments.
</long>
</locale>
</schema>
</value>
</entry>
<entry>
<key>visual_bell_type</key>
<value>
<schema>
<owner>metacity</owner>
<type>string</type>
<locale name="C">
<default_value>
<value>
<string>fullscreen</string>
</value>
</default_value>
<short>Visual Bell Type</short>
<long>
Tells Metacity how to implement the visual indication that the
system bell or another application 'bell' indicator has been
rung. Currently there are two valid values, "fullscreen", which
causes a fullscreen white-black flash, and "frame_flash" which
causes the titlebar of the application which sent the bell signal
to flash. If the application which sent the bell is unknown (as
is usually the case for the default "system beep"), the currently
focused window's titlebar is flashed.
</long>
</locale>
</schema>
</value>
</entry>
</entrylist>
</gconfentryfile>