| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we add the NetDevice pointer to the GPtrArray, we have
a single reference owned by the panel. When iterating over
this GPtrArray, no reference is taken.
The problem is that the code to handle command-line arguments
was unreferencing the NetDevices when iterating over it,
creating a disparity in the ref/unref pairs.
Fix that by simply not unreferencing the NetDevice instance
when iterating over it.
https://bugzilla.gnome.org/show_bug.cgi?id=786514
|
|
|
|
|
|
|
| |
We have it initialized and disposed and the async calls already handle
being cancelled. We just forgot to actually use it.
https://bugzilla.gnome.org/show_bug.cgi?id=786984
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=786984
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=786984
|
|
|
|
|
|
|
|
| |
The way it works is independent of the service so there's no reason
not to show it. We should also hide the remote-control-box widget
hierarchy since those can't be used here.
https://bugzilla.gnome.org/show_bug.cgi?id=786565
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows enabling screen sharing support under Wayland, as long as
the org.gnome.Mutter.RemoteDesktop D-Bus name is exported by mutter /
gnome-shell. That name will currently only be exported if the
corresponding experimental features has been added to mutter.
So far nothing is configurable, as gnome-remote-desktop is yet to be
configureable.
https://bugzilla.gnome.org/show_bug.cgi?id=786565
|
|
|
|
|
|
|
|
|
| |
Currently, while navigating using keyboard, the "Devices" and
"Details" rows of the GtkListBox in the sidebar don't seem to be
selected visually. Fix that by setting "selectable" property of those
two widgets as TRUE.
https://bugzilla.gnome.org/show_bug.cgi?id=786849
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Set hscrollbar_policy property of GtkScrolledWindow to never to
disable horizontal scrolling.
https://bugzilla.gnome.org/show_bug.cgi?id=785397
|
|
|
|
|
|
|
|
|
| |
Mutter currently generates 4 scales per integer scale. Knowing that,
we can nicely "round" the values we display to what the ideal scales
are even though the real values might be skewed since mutter creates
scale values close to the ideal ones that yield integer logical sizes.
https://bugzilla.gnome.org/show_bug.cgi?id=786922
|
|
|
|
|
| |
This is prone to miss intermediate values that users might actually
want to use so, for now, just show the 5 first scales.
|
|
|
|
|
|
|
|
|
| |
Mutter uses round() while we are just truncating via the implicit
double -> int type conversion, meaning that mutter will reject some
configurations that should work. Fix that by using the same rounding
as mutter.
https://bugzilla.gnome.org/show_bug.cgi?id=786919
|
|
|
|
|
|
|
| |
If we're cancelled, the panel is being finalized so return immediately
instead of iterating further and crashing.
https://bugzilla.gnome.org/show_bug.cgi?id=786097
|
|
|
|
|
|
|
| |
If we're cancelled the mount entries list might not have been totally
consumed so free it on finalize if needed.
https://bugzilla.gnome.org/show_bug.cgi?id=786097
|
|
|
|
|
|
|
| |
We were just plainly leaking them and there's really no need since
GCancellable instances can be re-used.
https://bugzilla.gnome.org/show_bug.cgi?id=786097
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
One digit isn't enough to distinguish between some modes. We probably
should do better mode filtering and/or grouping but that needs to
happen in mutter.
|
|
|
|
|
|
| |
Inactive monitors are not part of the configuration global geometry,
i.e. they don't have a position set, so it doesn't make sense to show
them.
|
|
|
|
| |
In this case just avoid showing information we don't have.
|
|
|
|
|
|
|
| |
We rely on visible-child-name notifications to generate the
appropriate UI, unfortunately it doesn't happen for the first added
stack page if the widget is already visible. Work around this by
adding a dummy page first.
|
|
|
|
|
|
|
|
|
| |
gtk_stack_set_visible_child_name() doesn't actually make a child
visible if the child widget isn't visible already which means we'd
always start in the first ("join") stack page even if the currently
applied configuration is one of the others.
https://bugzilla.gnome.org/show_bug.cgi?id=786767
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Settings panels are given 32px above and below their content
and 32px vertical space between major sections. 12px space is
placed below headings.
https://bugzilla.gnome.org/show_bug.cgi?id=786384
|