Skip to content

Commit

Permalink
Add button-placement key to Settings portal
Browse files Browse the repository at this point in the history
Signed-off-by: Dallas Strouse <[email protected]>
Co-authored-by: Emmanuele Bassi <[email protected]>
  • Loading branch information
orowith2os and ebassi committed Aug 24, 2023
1 parent fdb3157 commit 19ba62b
Show file tree
Hide file tree
Showing 2 changed files with 46 additions and 0 deletions.
23 changes: 23 additions & 0 deletions data/org.freedesktop.impl.portal.Settings.xml
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,29 @@
Unknown values should be treated as 0 (no preference).
</para></listitem>
</varlistentry>
<varlistentry>
<term>org.freedesktop.appearance button-placement (asas)</term>
<listitem><para>
Indicates the system's preferred arrangement of buttons on the titlebar.
In LTR locales, the first tuple is on the left (leading), and the second tuple is on the right (trailing).
In RTL locales, the first tuple is on the right (leading), and the second tuple is on the left (trailing).
Supported values are:
<simplelist>
<member>close: the close button</member>
<member>minimize: the minimize button</member>
<member>maximize: the maximize button</member>
</simplelist>
Unknown values must be ignored if the client does
not understand them. Duplicate buttons across the tuples and
string arrays are not allowed.
Examples:
<simplelist>
<member>`(["close","minimize","maximize"][])` would result in the close, minimize, and maximize buttons being drawn on the leading side of the window, in that order; there will be no buttons on the trailing side of the window.</member>
<member>`([]["close"])` would result in the close button being drawn on the trailing side of the window; there will be no buttons on the leading side of the window.</member>
<member>`(["close"]["maximize"])` would result in the close button being drawn on the leading side of the window, and the maximize button being drawn on the trailing side of the window.</member>
</simplelist>
</para></listitem>
</varlistentry>
</variablelist>
Implementations can provide other keys; they are entirely
Expand Down
23 changes: 23 additions & 0 deletions data/org.freedesktop.portal.Settings.xml
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,29 @@
Unknown values should be treated as 0 (no preference).
</para></listitem>
</varlistentry>
<varlistentry>
<term>org.freedesktop.appearance button-placement (asas)</term>
<listitem><para>
Indicates the system's preferred arrangement of buttons on the titlebar.
In LTR locales, the first tuple is on the left (leading), and the second tuple is on the right (trailing).
In RTL locales, the first tuple is on the right (leading), and the second tuple is on the left (trailing).
Supported values are:
<simplelist>
<member>close: the close button</member>
<member>minimize: the minimize button</member>
<member>maximize: the maximize button</member>
</simplelist>
Unknown values must be ignored if the client does
not understand them. Duplicate buttons across the tuples and
string arrays are not allowed.
Examples:
<simplelist>
<member>`(["close","minimize","maximize"][])` would result in the close, minimize, and maximize buttons being drawn on the leading side of the window, in that order; there will be no buttons on the trailing side of the window.</member>
<member>`([]["close"])` would result in the close button being drawn on the trailing side of the window; there will be no buttons on the leading side of the window.</member>
<member>`(["close"]["maximize"])` would result in the close button being drawn on the leading side of the window, and the maximize button being drawn on the trailing side of the window.</member>
</simplelist>
</para></listitem>
</varlistentry>
</variablelist>
Implementations can provide other keys; they are entirely
Expand Down

0 comments on commit 19ba62b

Please sign in to comment.