| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
If there are no connections or devices then we should not be showing
e.g. the Bluetooth list. Add a simple check that this is handled
correctly.
|
|
|
|
|
|
| |
This has the side effect of showing UI elements that should not be
visible at startup. Just add the correct gtk_widget_show calls to show
all relevant widgets.
|
|
|
|
|
| |
Otherwise the test might run on a develpers wayland session rather than
using the created X11 server.
|
|
|
|
|
|
| |
The disconnect was for the wrong object (connection rather than client).
Fix this by simply moving to use g_signal_connect_object which obsoletes
the explicit disconnect calls.
|
|
|
|
|
| |
When the connection is modified then the title might be changed. Call
the UI update function to ensure that widgets are updated.
|
|
|
|
|
|
|
|
|
|
| |
The test to check whether the Bluetooth (simple section) contains
elements was testing for NetObjectSimple. However, ethernet connections
are a subclass and check would count these. This causes issue when the
code is run after net object removal.
The fix is to check for the exact object type rather than also allowing
subclasses.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This never really worked on the new Setting layout
because it was historically implemented as "Back to
Overview", and we don't have an overview anymore.
This is fixed by morphing the implementation to be
"Back to previous panel", which forces us to actually
store the previous panel.
|
|
|
|
|
|
|
|
| |
There is no overview anymore -- Settings is always
visualizing a panel at any given time.
I just noticed that the Alt+Left shortcut was always
broken too. This will be fixed in a following commit.
|
|
|
|
|
|
| |
This reverts commit 94aeba51e311ce03a3f6cd5e78d8cb45f887267f.
We actually do want to see the last panel opened
|
| |
|
|
|
|
|
| |
It makes @feaneron happier, and fixes a couple of
memory leaks.
|
|
|
|
|
|
|
|
| |
This improves the snapping behaviour in a number of ways. It allows
increasing the snapping distance while still helping the user to align
monitors by snapping a different distance for the minor axis. The patch
also allows setting this distance to infinity so that we get the correct
behaviour in the case of two monitors for the corners.
|
|
|
|
|
|
|
| |
Two monitors are a special case where it is easy to ensure that the
monitors are always adjacent to each other by special casing the
snapping code. Do so by increasing the snapping distance to infinity and
adding extra snapping points so that corner cases are covered.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the following API:
* cc_display_config_get_ui_sorted_monitors
Returns the monitors in UI order
* cc_display_config_count_useful_monitors
Counts the useful monitors (active and usable)
* cc_display_monitor_is_useful
Checks if a monitor is active and usable
* cc_display_monitor_is_useable
Check if a monitor is marked as useable
* cc_display_monitor_set_usable
Used to mark builtin monitors as unusable if the lid is closed
* cc_display_monitor_get_ui_*
Get the UI number and strings for display
https://bugzilla.gnome.org/show_bug.cgi?id=786971
|
|
|
|
|
|
| |
The comment was not updated when the workaround in the code was removed.
https://bugzilla.gnome.org/show_bug.cgi?id=786971
|
|
|
|
|
|
|
|
|
| |
Remove the code that has become unused with the new arrangement widget.
There are more possible cleanups as there is some code duplication
between cc-display-panel.c and cc-display-arrangment.c at this point.
https://bugzilla.gnome.org/show_bug.cgi?id=786971
|
|
|
|
|
|
|
|
|
|
| |
This commits adds a new arrangement widget, refactoring the existing
code and addressing a number of issues:
* Forced snapping made laying out more than 2 monitors hard
* Random gaps would be shown between monitors
* The scaling was fixed and usually tiny
https://bugzilla.gnome.org/show_bug.cgi?id=786971
|
|
|
|
|
|
| |
This is in preparation to a new arrangement widget.
https://bugzilla.gnome.org/show_bug.cgi?id=786971
|
|
|
|
| |
This commit has no functional changes.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
GNOME master image is not working, so, we are using a workaround.
|
| |
|
|
|
|
| |
It is needed to make things faster.
|
|
|
|
|
|
| |
Replaces usage of deprecated GdkScreen API. We still have to pass
monitor numbers around for gdk_window_fullscreen_on_monitor(), such
is life.
|
|
|
|
| |
Replaces usage of deprecated API.
|
|
|
|
| |
Replaces usage of deprecated API.
|
| |
|
|
|
|
| |
It now has a new, on by default, libpsl dependency.
|
| |
|
| |
|
|
|
|
| |
These files are not relevant anymore these days.
|
| |
|
| |
|
| |
|
|
|
|
| |
[skip ci]
|
| |
|
|
|
|
| |
[skip ci]
|
|
|
|
| |
Make the flatpak routine able to deal with patches (if needed).
|
| |
|
|
|
|
|
| |
Providing autocleanups for types you don't own is not a good idea, since
it breaks when upstream adds those autocleanups.
|
|
|
|
|
| |
The goal is dogfooding. Allow interested people to try, safely, the
bleeding GNOME Control Center.
|