There's a few differences in how onComplete is run:
- We need to run moveDone on every clone transition, as the transitions aren't
done when cloneContainer's transition finishes
- We cannot run layout until startup is done. For some reason onComplete runs
before monitor setup is done properly.
squash! Use clutter animations
- Can't use addTween as a timeout, but transitions are now finished when
onComplete is run, so there's no need for this anymore.
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
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
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.
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.
Defaults to true. If false uses gnome shell's `Activities` text and hides the
workspace labels.
Set to false like this:
```
Extension.imports.convenience.getSettings()
.set_boolean('use-workspace-name', false)
```
Installing and enabling the extension didn't work, as some stuff accessed
`TopBar.menu` too early. This was a pretty bad bug, that was fixed, but then
reverted.
Per workspace settings can be accessed through `space.settings`.
A setting's path is stored under its uuid in
`/org/gnome/shell/extensions/paperwm/workspaces/${uuid}/`. When modifying a
workspace setting the uuid will be recorded in
`org.gnome.Shell.Extensions.PaperWM.WorkspaceList`.
Spaces get their settings by looking for an uuid with an `index` key
corrosponding to its `workspace.index()`. If such a setting can't be found the
space will be given a fresh uuid and the name and color will be assigned as
before.
