isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-12-11 22:10:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
84d48254d7
mutter/data/org.gnome.mutter.gschema.xml.in

185 lines
6.9 KiB
XML
Raw Normal View History

Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
<schemalist>
gschema: Turn experimental features into flags Defining valid values makes 1. changing settings less error prone 2. sure they are discoverable. This does reset the values once on update, but fortunately does *not* change the way to set the values. Thus e.g. enabling fractional scaling via terminal command still works as before and internet guides stay valid. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1961>
2021-08-09 10:07:14 +00:00
<flags id="org.gnome.mutter.MetaExperimentalFeature">
<value nick="scale-monitor-framebuffer" value="1"/>
<value nick="kms-modifiers" value="2"/>
backends/native: Main thread rt-scheduler: experimental feature no more To paraphrase jadahl: we have a dedicated KMS thread now, which also has realtime scheduling enabled unconditionally. realtime scheduling on the main thread isn't too great of an idea, considering GC can take a hot minute. And to quote rmader: we most likely won't be able to make the main thread rt as long as we use GJS and thus have GC. So let's get rid of it! It's just been breaking things anyways. This just ignores the setting; we'll fully remove it when GNOME 46 comes around. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3296>
2023-10-18 21:34:15 +00:00
<value nick="autoclose-xwayland" value="4"/>
gschema: Turn experimental features into flags Defining valid values makes 1. changing settings less error prone 2. sure they are discoverable. This does reset the values once on update, but fortunately does *not* change the way to set the values. Thus e.g. enabling fractional scaling via terminal command still works as before and internet guides stay valid. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1961>
2021-08-09 10:07:14 +00:00
</flags>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
<schema id="org.gnome.mutter" path="/org/gnome/mutter/"
data: fix gettext domain https://bugzilla.gnome.org/show_bug.cgi?id=691611
2017-08-09 10:08:05 +00:00
gettext-domain="@GETTEXT_DOMAIN@">
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
<key name="overlay-key" type="s">
<default>'Super_L'</default>
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
<summary>Modifier to use for extended window management operations</summary>
<description>
Use Unicode in translatable strings See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772218
2016-09-29 22:56:23 +00:00
This key will initiate the “overlay”, which is a combination window
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
overview and application launching system. The default is intended
Use Unicode in translatable strings See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772218
2016-09-29 22:56:23 +00:00
to be the “Windows key” on PC hardware.
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
Use Unicode in translatable strings See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772218
2016-09-29 22:56:23 +00:00
It’s expected that this binding either the default or set to
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
the empty string.
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
</description>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
</key>
<key name="attach-modal-dialogs" type="b">
<default>false</default>
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
<summary>Attach modal dialogs</summary>
<description>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
When true, instead of having independent titlebars, modal dialogs
appear attached to the titlebar of the parent window and are moved
together with the parent window.
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
</description>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
</key>
<key name="edge-tiling" type="b">
<default>false</default>
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
<summary>Enable edge tiling when dropping windows on screen edges</summary>
<description>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
If enabled, dropping windows on vertical screen edges maximizes them
vertically and resizes them horizontally to cover half of the available
area. Dropping windows on the top screen edge maximizes them completely.
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
</description>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
</key>
prefs: Add dynamic-workspaces setting We currently sync the number of workspaces with the corresponding preference. This is not really useful with GNOME Shell's dynamic handling of workspaces, not least as the setting is effectively ignored. Worse, it will trigger writes to dconf on login, slowing down startup, so add a setting to indicate that workspaces are managed dynamically and really ignore the num-workspaces setting when set. https://bugzilla.gnome.org/show_bug.cgi?id=671568
2012-03-08 00:29:58 +00:00
<key name="dynamic-workspaces" type="b">
<default>false</default>
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
<summary>Workspaces are managed dynamically</summary>
<description>
prefs: Add dynamic-workspaces setting We currently sync the number of workspaces with the corresponding preference. This is not really useful with GNOME Shell's dynamic handling of workspaces, not least as the setting is effectively ignored. Worse, it will trigger writes to dconf on login, slowing down startup, so add a setting to indicate that workspaces are managed dynamically and really ignore the num-workspaces setting when set. https://bugzilla.gnome.org/show_bug.cgi?id=671568
2012-03-08 00:29:58 +00:00
Determines whether workspaces are managed dynamically or
Use Unicode in translatable strings See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772218
2016-09-29 22:56:23 +00:00
whether there’s a static number of workspaces (determined
prefs: Add dynamic-workspaces setting We currently sync the number of workspaces with the corresponding preference. This is not really useful with GNOME Shell's dynamic handling of workspaces, not least as the setting is effectively ignored. Worse, it will trigger writes to dconf on login, slowing down startup, so add a setting to indicate that workspaces are managed dynamically and really ignore the num-workspaces setting when set. https://bugzilla.gnome.org/show_bug.cgi?id=671568
2012-03-08 00:29:58 +00:00
by the num-workspaces key in org.gnome.desktop.wm.preferences).
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
</description>
prefs: Add dynamic-workspaces setting We currently sync the number of workspaces with the corresponding preference. This is not really useful with GNOME Shell's dynamic handling of workspaces, not least as the setting is effectively ignored. Worse, it will trigger writes to dconf on login, slowing down startup, so add a setting to indicate that workspaces are managed dynamically and really ignore the num-workspaces setting when set. https://bugzilla.gnome.org/show_bug.cgi?id=671568
2012-03-08 00:29:58 +00:00
</key>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
<key name="workspaces-only-on-primary" type="b">
<default>false</default>
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
<summary>Workspaces only on primary</summary>
<description>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
Determines whether workspace switching should happen for windows
on all monitors or only for windows on the primary monitor.
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
</description>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
</key>
display: (Optionally) delay focus changes in focus-follows-mouse mode Moving focus immediately on crossing events as we currently do in focus-follows-mouse mode may trigger a lot of unwanted focus changes when moving over unrelated windows on the way to a target. Those accidental focus changes prevent features like GNOME Shell's application menu from working properly and are visually expensive since we now use a very distinct style for unfocused windows. Instead, delay the actual focus change until the pointer has stopped moving. https://bugzilla.gnome.org/show_bug.cgi?id=678169
2012-08-29 02:38:54 +00:00
<key name="focus-change-on-pointer-rest" type="b">
<default>false</default>
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
<summary>Delay focus changes until the pointer stops moving</summary>
<description>
Use Unicode in translatable strings See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772218
2016-09-29 22:56:23 +00:00
If set to true, and the focus mode is either “sloppy” or “mouse”
display: (Optionally) delay focus changes in focus-follows-mouse mode Moving focus immediately on crossing events as we currently do in focus-follows-mouse mode may trigger a lot of unwanted focus changes when moving over unrelated windows on the way to a target. Those accidental focus changes prevent features like GNOME Shell's application menu from working properly and are visually expensive since we now use a very distinct style for unfocused windows. Instead, delay the actual focus change until the pointer has stopped moving. https://bugzilla.gnome.org/show_bug.cgi?id=678169
2012-08-29 02:38:54 +00:00
then the focus will not be changed immediately when entering a
window, but only after the pointer stops moving.
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
</description>
display: (Optionally) delay focus changes in focus-follows-mouse mode Moving focus immediately on crossing events as we currently do in focus-follows-mouse mode may trigger a lot of unwanted focus changes when moving over unrelated windows on the way to a target. Those accidental focus changes prevent features like GNOME Shell's application menu from working properly and are visually expensive since we now use a very distinct style for unfocused windows. Instead, delay the actual focus change until the pointer has stopped moving. https://bugzilla.gnome.org/show_bug.cgi?id=678169
2012-08-29 02:38:54 +00:00
</key>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
<key name="draggable-border-width" type="i">
<default>10</default>
<range min="0" max="64"/>
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
<summary>Draggable border width</summary>
<description>
Use Unicode in translatable strings See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772218
2016-09-29 22:56:23 +00:00
The amount of total draggable borders. If the theme’s visible
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
borders are not enough, invisible borders will be added to meet
this value.
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
</description>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
</key>
automaximize: Make it optional Make automaximize optional by adding a gsetting "auto-maximize" (defaults to true). https://bugzilla.gnome.org/show_bug.cgi?id=680990
2012-09-08 09:34:27 +00:00
<key name="auto-maximize" type="b">
<default>true</default>
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
<summary>Auto maximize nearly monitor sized windows</summary>
<description>
settings: Clarifiy auto_maximize language Use less technical terms and fix a typo. https://bugzilla.gnome.org/show_bug.cgi?id=680990
2013-02-14 18:59:57 +00:00
If enabled, new windows that are initially the size of the monitor
automatically get maximized.
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
</description>
automaximize: Make it optional Make automaximize optional by adding a gsetting "auto-maximize" (defaults to true). https://bugzilla.gnome.org/show_bug.cgi?id=680990
2012-09-08 09:34:27 +00:00
</key>
prefs: Add center-new-windows setting
2014-04-25 13:26:24 +00:00
<key name="center-new-windows" type="b">
<default>false</default>
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
<summary>Place new windows in the center</summary>
<description>
prefs: Add center-new-windows setting
2014-04-25 13:26:24 +00:00
When true, the new windows will always be put in the center of the
active screen of the monitor.
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-22 00:13:54 +00:00
</description>
prefs: Add center-new-windows setting
2014-04-25 13:26:24 +00:00
</key>
gschema: Turn experimental features into flags Defining valid values makes 1. changing settings less error prone 2. sure they are discoverable. This does reset the values once on update, but fortunately does *not* change the way to set the values. Thus e.g. enabling fractional scaling via terminal command still works as before and internet guides stay valid. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1961>
2021-08-09 10:07:14 +00:00
<key name="experimental-features"
flags='org.gnome.mutter.MetaExperimentalFeature'>
Remove old monitor configuration system Remove the old MetaMonitorConfig system and mark the new one as non-experimental. This also removes the D-Bus property. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-24 07:36:12 +00:00
<default>[]</default>
backend: Add 'experimental-features' gsetting This gsetting will allow the adding of keywords to a array, where each keyword may enable an experimental feauter, if the given mutter version supports that particular experimental feature. Emphasis is put on the lack of guarantee that any such keyword has any effect. Currently no keywords are defined. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 09:48:19 +00:00
<summary>Enable experimental features</summary>
<description>
To enable experimental features, add the feature keyword to the list.
Whether the feature requires restarting the compositor depends on the
given feature. Any experimental feature is not required to still be
Use Unicode in a new translatable string See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772218
2017-04-07 17:25:12 +00:00
available, or configurable. Don’t expect adding anything in this
backend: Add 'experimental-features' gsetting This gsetting will allow the adding of keywords to a array, where each keyword may enable an experimental feauter, if the given mutter version supports that particular experimental feature. Emphasis is put on the lack of guarantee that any such keyword has any effect. Currently no keywords are defined. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 09:48:19 +00:00
setting to be future proof.
Add support for scaled logical monitor framebuffers This commit adds support for rendering onto enlarged per logical monitor framebuffers, using the scaled clutter stage views, for HiDPI enabled logical monitors. This works by scaling the mode of the monitors in a logical monitors by the scale, no longer relying on scaling the window actors and window geometry for making windows have the correct size on HiDPI monitors. It is disabled by default, as in automatically created configurations will still use the old mode. This is partly because Xwayland clients will not yet work good enough to make it feasible. To enable, add the 'scale-monitor-framebuffer' keyword to the org.gnome.mutter.experimental-features gsettings array. It is still possible to specify the mode via the new D-Bus API, which has been adapted. The adaptations to the D-Bus API means the caller need to be aware of how to position logical monitors on the stage grid. This depends on the 'layout-mode' property that is used (see the DisplayConfig D-Bus documentation). https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 10:10:52 +00:00
Currently possible keywords:
Use Unicode in a new translatable string See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772218
2017-04-07 17:25:12 +00:00
• “scale-monitor-framebuffer” — makes mutter default to layout logical
Add support for scaled logical monitor framebuffers This commit adds support for rendering onto enlarged per logical monitor framebuffers, using the scaled clutter stage views, for HiDPI enabled logical monitors. This works by scaling the mode of the monitors in a logical monitors by the scale, no longer relying on scaling the window actors and window geometry for making windows have the correct size on HiDPI monitors. It is disabled by default, as in automatically created configurations will still use the old mode. This is partly because Xwayland clients will not yet work good enough to make it feasible. To enable, add the 'scale-monitor-framebuffer' keyword to the org.gnome.mutter.experimental-features gsettings array. It is still possible to specify the mode via the new D-Bus API, which has been adapted. The adaptations to the D-Bus API means the caller need to be aware of how to position logical monitors on the stage grid. This depends on the 'layout-mode' property that is used (see the DisplayConfig D-Bus documentation). https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 10:10:52 +00:00
monitors in a logical pixel coordinate
space, while scaling monitor
framebuffers instead of window content,
to manage HiDPI monitors. Does not
require a restart.
gschema: really use line breaks in schema The newline character `\n` in the schema does not produce a new line. Use a newline instead. fixes: dbe44f3a83e6a6bdc611bb298e3781a0aebbbd7b https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1483
2020-10-08 14:27:56 +00:00
gschema: Make 'kms-modifiers' only about scanout buffers It's not used to determine what we send to Wayland clients anymore, it does so by default. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2146>
2021-12-08 21:02:30 +00:00
• “kms-modifiers” — makes mutter always allocate scanout
buffers with explicit modifiers, if
supported by the driver. Requires a
restart.
gschema: Add "kms-modifiers" experimental feature description To make it more discoverable. While on it, fix a typo. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1961>
2021-08-09 09:46:15 +00:00
gschema: Fix capitalization of autoclose-xwayland option Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1696>
2021-02-01 17:51:27 +00:00
• “autoclose-xwayland” — automatically terminates Xwayland if all
xwayland: Use Xwayland auto-terminate feature When using Xwayland-on-demand (default), if the (experimental) autoclose features is enabled, we can rely on Xwayland's auto-terminate feature instead of explicitly killing the Xwayland process. With it, gone is the mechanism that was added to check the X11 clients connected and their executable to check whether we can (safely) kill Xwayland. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1794>
2021-03-17 15:18:54 +00:00
relevant X11 clients are gone.
Requires a restart.
xwayland: Make autoclose-xwayland an exp. feature Closing automatically Xwayland once all relevant X11 clients are gone is inherently racy, if a new client comes along right at the time we're killing Xwayland. Fixing the possible race conditions between mutter, Xwayland and the X11 clients may take some time. Meanwhile, make that an experimental feature "autoclose-xwayland". Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1673>
2021-01-18 16:59:08 +00:00
backend: Add 'experimental-features' gsetting This gsetting will allow the adding of keywords to a array, where each keyword may enable an experimental feauter, if the given mutter version supports that particular experimental feature. Emphasis is put on the lack of guarantee that any such keyword has any effect. Currently no keywords are defined. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 09:48:19 +00:00
</description>
</key>
keybindings: Trigger locate-pointer on key modifier We trigger the "locate-pointer" mechanism when a special key modifier (defaults to Control_L) key is pressed and released. https://gitlab.gnome.org/GNOME/mutter/merge_requests/453 https://gitlab.gnome.org/GNOME/gnome-shell/issues/981 https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/merge_requests/19 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/86
2019-02-20 10:53:54 +00:00
<key name="locate-pointer-key" type="s">
<default>'Control_L'</default>
<summary>Modifier to use to locate the pointer</summary>
<description>
This key will initiate the “locate pointer” action.
</description>
</key>
display: Make check-alive timeout configureable The check-alive feature is there for the user to be able to terminate frozen applications more easily. However, sometimes applications are implemented in a way where they fail to be reply to ping requests in a timely manner, resulting in that, to the compositor, they are indistinguishable from clients that have frozen indefinitely. When using an application that has these issues, the GUI showed in response to the failure to respond to ping requests can become annoying, as it disrupts the visual presentation of the application. To allow users to work-around these issues, add a setting allowing them to configure the timeout waited until an application is considered frozen, or disabling the check completely. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1080
2020-02-21 20:03:16 +00:00
<key name="check-alive-timeout" type="u">
<default>5000</default>
<summary>Timeout for check-alive ping</summary>
<description>
Number of milliseconds a client has to respond to a ping request in
order to not be detected as frozen. Using 0 will disable the alive check
completely.
</description>
</key>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
<child name="keybindings" schema="org.gnome.mutter.keybindings"/>
</schema>
<schema id="org.gnome.mutter.keybindings" path="/org/gnome/mutter/keybindings/">
keybindings: Add toggle-tile-left/right bindings Having keybindings for side-by-side tiling has been requested for a long time, so add this support now. https://bugzilla.gnome.org/show_bug.cgi?id=648700
2011-11-15 16:29:56 +00:00
<key name="toggle-tiled-left" type="as">
<default><![CDATA[['<Super>Left']]]></default>
gschema: Add missing summaries for toggle-tiled-left/toggle-tiled-right Wording copied from `data/50-mutter-windows.xml`. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1573>
2020-11-18 21:48:08 +00:00
<summary>View split on left</summary>
keybindings: Add toggle-tile-left/right bindings Having keybindings for side-by-side tiling has been requested for a long time, so add this support now. https://bugzilla.gnome.org/show_bug.cgi?id=648700
2011-11-15 16:29:56 +00:00
</key>
<key name="toggle-tiled-right" type="as">
<default><![CDATA[['<Super>Right']]]></default>
gschema: Add missing summaries for toggle-tiled-left/toggle-tiled-right Wording copied from `data/50-mutter-windows.xml`. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1573>
2020-11-18 21:48:08 +00:00
<summary>View split on right</summary>
keybindings: Add toggle-tile-left/right bindings Having keybindings for side-by-side tiling has been requested for a long time, so add this support now. https://bugzilla.gnome.org/show_bug.cgi?id=648700
2011-11-15 16:29:56 +00:00
</key>
keybindings: Add a switch-monitor builtin keybinding Moved from g-s-d's media keys plugin, where it was called "video-out", since it requires changing the current monitor configuration and we want to remove the old DBus API. This implementation is intentionally simple and not really meant for more than debugging and validating the various configurations. A better user experience will be introduced in gnome-shell with a custom keybinding handler. The default value includes <Super>P in addition to the standard keysym for historical reasons. https://bugzilla.gnome.org/show_bug.cgi?id=781906
2017-06-07 17:07:26 +00:00
<key name="switch-monitor" type="as">
<default><![CDATA[['<Super>p','XF86Display']]]></default>
<summary>Switch monitor configurations</summary>
</key>
keybindings: Add a rotate-monitor builtin keybinding Moved from g-s-d's media keys plugin, where it was called "video-rotate", since it requires changing the current monitor configuration and we want to remove the old DBus API. https://bugzilla.gnome.org/show_bug.cgi?id=781906
2017-05-05 15:51:06 +00:00
<key name="rotate-monitor" type="as">
<default><![CDATA[['XF86RotateWindows']]]></default>
<summary>Rotates the built-in monitor configuration</summary>
</key>
input-capture: Hook up capturing of events to active session This adds the actual input capturing rerouting that takes events and first hands them to the input capture session, would it be active. Events are right now not actually processed in any way, but will eventually be passed to a libei client using libeis. A key binding for allowing cancelling the capture session is added (defaults to <Super><Shift>Escape) to avoid getting stuck in case the client doesn't even terminate the session. The added test case makes sure that the pointer moves again after pressing the keybinding. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2628>
2022-04-27 08:50:43 +00:00
<key name="cancel-input-capture" type="as">
<default><![CDATA[['<Super><Shift>Escape']]]></default>
<summary>Cancel any active input capture session</summary>
</key>
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 16:14:15 +00:00
</schema>
</schemalist>
Reference in New Issue Copy Permalink