dconf can't reliable get default values(?)
According to https://bugzilla.redhat.com/show_bug.cgi?id=1541448 the dconf
default value might also differ from the gsettings default value(?)
I did not find a way to differentiate between "use default value" and the actual
default value - so running the script might change some settings from "use
default value" to the actual default value.
IIUC 'gsettings' require the gsettings daemon to run, while 'dconf' is lower
level and modify the database directly.
Fixes#121
With #73 resolved (cd95ad220) we can tolerate changes to workarea across
workspaces.
Extensions that rely on workarea.y (eg. upright dash-to-dock) will no longer be
broken.
Note that (3.28) only windows with visible actors are affected (immediately) by
workarea changes so changing workspace from without-top-bar (A) to
with-top-bar (B) only cause resizes of B's visible windows.
Workspace navigation by itself (shows the topbar) does not cause resizes. (eg.
initiate and cancel a navigation)
Navigation between without-top-bar workspaces does not cause resizes.
This reverts commit 86283c5dea
This reverts commit 20809ad6b0
A freeze can be triggered like this: (might have to run the resize twice)
metaWindow.connect('size-changed', () => {
let f = metaWindow.get_frame_rect()
metaWindow.move_resize_frame(true, f.x, f.y, f.width, 500)
})
let f = metaWindow.get_frame_rect()
metaWindow.move_resize_frame(true, f.x, f.y, f.width, f.height-50)
Fixes#73
Caused problems when switching to workspaces without topbar - probably because
the topbar is briefly shown during navigation - restricting the workarea -
resizing the windows in the workspace without topbar - causing the dreaded #73.
This conjecture is not verified, but disabling the affectsStruts fixes the
symptoms :)
Fixes#108
Use the tiling to sort the overview. Floating windows are sorted the regular way
among themselves and put before the tiled windows.
We also report the correct coordinates so animation to and from the overview is
correct.
ref #4
We don't use workarea.y directly as it can cause problems cause problems if eg.
a layout is triggered when a fullscreen window is active. Instead we scale the
panel height with `space.showTopBar`.
Was not intended for master.
Revert "don't use workarea.y directly"
This reverts commit cb67f451a2.
Revert "space: connect settings"
This reverts commit 3c7ac9509e.
Revert "fixup! workspace menu: add zen toggle"
This reverts commit bff403c134.
Revert "workspace menu: add zen toggle"
This reverts commit 89bae34412.
Revert "Implement"
This reverts commit dd812e5714.
Revert "workspace schema: add `show-top-bar`"
This reverts commit 7dcac8896a.
Using a SwitcherPopup was just tiresome and made it difficult to fix some
issues.
This fixes a lot of the issues with #70, though eg. alt-tab still leaks
Mutter copiled without checks makes showing an unmapped StEntry with initial
text crash the shell.
Work around this by using `hint-text` and only updating the `text` property if
it's been set by the focus signal at some point.
TODO: Making the entry without a button makes the tracking obsolete as we update
the workspace name all the time. It's also probably just as good.
Mutter 3.32 is built with `G_DISABLE_CHECKS` which disables among other things
`g_return_if_fail`.
This makes `set_child_below/above_sibling` remove the child if it's the same as
sibling, but leaves the child with a parent link.
Tor Hedin Brønner