Settings merge requestshttps://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests2024-03-27T14:14:54Zhttps://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1833Add "legacy HiDPI" toggle and implement scaling mockups2024-03-27T14:14:54ZJonas ÅdahlAdd "legacy HiDPI" toggle and implement scaling mockupsThis makes it look like this, if `scale-monitor-framebuffer` is enabled. Note! This does *NOT* toggle said setting; it relies on the corresponding functionality being enabled by something else. That means downstream patching, manual edit...This makes it look like this, if `scale-monitor-framebuffer` is enabled. Note! This does *NOT* toggle said setting; it relies on the corresponding functionality being enabled by something else. That means downstream patching, manual editing the gsetting, or at some point when it's decided that this should be enabled by default.
The "legacy HiDPI" toggle makes GNOME Shell switch between the "new" and "old" way without manipulating any experimental gsettings. This does not need any mutter changes, as it has been part of the D-Bus API for some years already.
Disclaimer: I'm not very well experienced in building GUIs, so please be gentle. The text preview thing is implemented using `GtkScrollableWindow` and an enlarged `GtkInscription`. I went with the Pango sample text instead of the Lorem Ipsum stuff - it is translated thus more relevant, especially for non-Latin-like languages.
It looks like this:
![Screenshot_from_2023-06-20_15-31-31](/uploads/29d96e57eb516e007bae700da4da5ed0/Screenshot_from_2023-06-20_15-31-31.png)
![Screenshot_from_2023-06-20_15-31-57](/uploads/ea6991322cae430741f7f48eb319b18c/Screenshot_from_2023-06-20_15-31-57.png)
Mockups can be found here: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2516.
Some open questions I didn't find answers to in the mockups:
* There is no easy way to tell what scale active. The bold percent is for the default/preferred scale. The one with the blue frame is for the currently selected/pending scale.
* The mockups limits the selectable scales to 5. When the preferred/default is e.g. 250%, that means the current implementation shows 2 below, and 2 above, meaning the lowest is 200%. Not sure this is the best way to handle it.GNOME 47https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/2286Draft: display: Add toggle to configure XWayland scaling2024-02-27T09:05:35ZJonas DreßlerDraft: display: Add toggle to configure XWayland scalingMutter supports a mode now where XWayland clients can scale themselves up
to an integer scale factor, instead of being scaled up by the compositor.
While it works nicely with most x11 apps, it's making old x11 apps (which
can't do scalin...Mutter supports a mode now where XWayland clients can scale themselves up
to an integer scale factor, instead of being scaled up by the compositor.
While it works nicely with most x11 apps, it's making old x11 apps (which
can't do scaling themselves) too small.
As a practical way to deal with this, let's expose a toggle for this in the
display panel to change the behavior to let mutter scale xwayland clients
(instead of clients scaling up themselves).
Hopefully we can at some point hide this toggle when no XWayland apps are
installed anymore.
Marked as Draft because the design for the toggle isn't finished yet.
Goes together with https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3567 and https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/353.
--
Screenshot
![Screenshot_from_2024-02-19_19-53-21](/uploads/fd4eabded2cddac2b55a569af0078840/Screenshot_from_2024-02-19_19-53-21.png)https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/977Draft: Add brightness controls to night light options2023-08-29T12:46:38ZNishal KulkarniDraft: Add brightness controls to night light optionsAdd UI controls for setting dim and default brightness.
Necessary for new feature that may be added to gnome-settings-daemon
Using 2 spin buttons instead of a single slider because
while the slider allowed for setting dim brightness le...Add UI controls for setting dim and default brightness.
Necessary for new feature that may be added to gnome-settings-daemon
Using 2 spin buttons instead of a single slider because
while the slider allowed for setting dim brightness level,
I couldn't figure out a way to revert to the brightness before
nightlight was enabled.
By allowing the user to set the default brightness level,
it becomes easier to reset the brightness when night light is off.
More information about the feature can be found in the GSD MR
GSD MR: gnome-settings-daemon!230
Closes GSD Issue: gnome-settings-daemon#528https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1864Draft: mouse-panel, display: Use AdwToggleGroup2023-11-29T18:57:37ZChristopher DavisDraft: mouse-panel, display: Use AdwToggleGrouplibadwaita provides a new widget for exclusive toggles that
we can use in place of our linked styling that we were using
previously. AdwToggleGroup handles displaying the buttons,
icons, and tooltips in a nice, compact, and accessible wi...libadwaita provides a new widget for exclusive toggles that
we can use in place of our linked styling that we were using
previously. AdwToggleGroup handles displaying the buttons,
icons, and tooltips in a nice, compact, and accessible widget.
Requires https://gitlab.gnome.org/GNOME/libadwaita/-/merge_requests/727https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1721Draft: Apply display settings to GDM session2023-03-22T13:09:05ZRastersoftDraft: Apply display settings to GDM sessionThis MR builds over https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1580
This commit changes the way this works. Instead of launching the daemon as the GDM user, it is launched as root. It copies the monitors.xml fi...This MR builds over https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1580
This commit changes the way this works. Instead of launching the daemon as the GDM user, it is launched as root. It copies the monitors.xml file into /etc/xdg, and generates a dconf db file that is stored at /etc/dconf/db/gdm.d, and compiled.
Unfortunately, although the monitors.xml do work, the dconf part doesn't.https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/698Display settings can fail to to both hardware and software issues2023-04-12T14:04:09ZAaron Honeycuttaaron@system76.comDisplay settings can fail to to both hardware and software issuesAfter speaking to my coworker at system76 and experiencing a display issue where we swapped cables and the issue was still there the wording can be a bit better. The core issue in our case was that one display was covered by the other in...After speaking to my coworker at system76 and experiencing a display issue where we swapped cables and the issue was still there the wording can be a bit better. The core issue in our case was that one display was covered by the other in the Display Settings and moving that allowed us to apply the changes (we found this since we could mirror the displays with no issue).https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/2303display: Add an icon to the Night Light row2024-02-21T01:12:23ZAutomeris naranjadisplay: Add an icon to the Night Light row(Needs design team approval)
Add an icon to the Night Light row, like the Proxy row from the Network panel:
![Screenshot_from_2024-02-20_21-48-45](/uploads/74b16278a626a6e29eee04fc502df7d2/Screenshot_from_2024-02-20_21-48-45.png)(Needs design team approval)
Add an icon to the Night Light row, like the Proxy row from the Network panel:
![Screenshot_from_2024-02-20_21-48-45](/uploads/74b16278a626a6e29eee04fc502df7d2/Screenshot_from_2024-02-20_21-48-45.png)https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1849Draft: cleanup: Port certain switch rows to AdwSwitchRow2024-03-25T23:35:46ZBilal Elmoussaouibil.elmoussaoui@gmail.comDraft: cleanup: Port certain switch rows to AdwSwitchRowI didn't port all of them, got lazy sorry.
Do not merge yet, I have noticed that the datetime panel uses the `state-set` signal which need to be ported to notify::active.I didn't port all of them, got lazy sorry.
Do not merge yet, I have noticed that the datetime panel uses the `state-set` signal which need to be ported to notify::active.