Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gnome-shell gnome-shell
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,042
    • Issues 2,042
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 152
    • Merge requests 152
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • gnome-shellgnome-shell
  • Merge requests
  • !1264

calendar: Fix initial do-not-disturb state

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Florian Müllner requested to merge fmuellner/gnome-shell:initial-dnd-state into master May 18, 2020
  • Overview 1
  • Commits 1
  • Pipelines 2
  • Changes 1

The do-not-disturb button and the contained switch are tied together via a bidirectional property binding.

However it still matters which objects are used as source and target, as that will determine the initial state: Right now the (unchecked) button is used as source, which means that do-not-disturb is turned off on startup.

We want the state to be preserved, so swap source and target to let the switch (that is bound to the underlying GSetting) control the initial state.

Fixes #2804 (closed)

Edited May 18, 2020 by Florian Müllner
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: initial-dnd-state