1. 28 May, 2018 4 commits
  2. 17 Apr, 2018 1 commit
  3. 07 Apr, 2018 1 commit
  4. 16 Mar, 2018 1 commit
  5. 23 Feb, 2018 1 commit
  6. 23 Jan, 2018 1 commit
  7. 18 Jan, 2018 2 commits
  8. 17 Jan, 2018 2 commits
  9. 28 Nov, 2017 1 commit
  10. 20 Aug, 2017 2 commits
    • Allan Day's avatar
      Harmonize list box row layouts · 87568e92
      Allan Day authored
      While it isn't possible, or even advisable, to make all the list
      box rows the same height, using a number of standard heights will
      make the control center feel more harmoneous.
      Adust the height of the list box rows in Color, Date & Time,
      Mouse & Touchpad, Network, Privacy, Region & Language, Sharing
      and Universal Access. Makes standard rows that contain labels
      and/or controls 58px tall. Some other rows, such as those which
      contain two lines of text, are allowed to be taller.
    • Allan Day's avatar
      Standardize vertical spacing of panels · 8a8e53ab
      Allan Day authored
      Ensure that the vertical spacing inside each panel is similar.
      This makes the transition between each panel smoother and makes
      the control center feel more cohesive.
      Settings panels are given 32px above and below their content
      and 32px vertical space between major sections. 12px space is
      placed below headings.
      Bluetooth, displays and printers are not addressed.
  11. 09 Aug, 2017 1 commit
  12. 10 Jul, 2017 3 commits
  13. 30 May, 2017 3 commits
  14. 25 May, 2017 1 commit
  15. 02 May, 2017 1 commit
  16. 29 Nov, 2016 1 commit
  17. 03 Oct, 2016 1 commit
  18. 30 Aug, 2016 1 commit
    • Rui Matos's avatar
      region: Avoid a crash on panel destruction · bbdcaaa0
      Rui Matos authored
      GtkListBox might emit the row-selected signal while being destroyed
      and our row-selected handler accesses widgets owned by GtkBuilder so,
      depending on the order on which the builder destroys its objects, we
      could crash on the signal handler when destroying the builder.
      Using g_signal_connect_object() avoids this issue by disconnecting us
      before our finalize() runs.
  19. 23 Aug, 2016 1 commit
  20. 14 Jun, 2016 1 commit
  21. 25 May, 2016 1 commit
  22. 13 May, 2016 2 commits
  23. 28 Apr, 2016 1 commit
  24. 07 Apr, 2016 1 commit
  25. 11 Feb, 2016 1 commit
  26. 18 Jan, 2016 2 commits
    • Jiro Matsuzawa's avatar
    • Rui Matos's avatar
      region: Ensure that system and user formats are consistent · 30470d72
      Rui Matos authored
      The formats (or 'region') setting might be unset meaning that it's the
      same as the language since that's what LC_TIME et al default to when
      We already handle this for the user setting but for the system setting
      we're losing that semantic when getting it from localed since we don't
      allow priv->system_region to remain unset. This means that when users
      change the system language, the system formats will be explicitly set
      to the previous value of the system language instead of remaining
      unset and thus follow the new value for the system language.
      This isn't that bad on multi user systems where we display system
      settings separately from user settings, but on single user systems we
      change the system values to match the user values which, due to the
      above mentioned semantic difference regarding the region setting,
      means that when changing the language, the (unset) region will be
      displayed as the same as the language but the system region will be
      explicitly set to the previous language.
      Fix this by making the system region have the same semantic as the
      user's, i.e. allow it to remain unset until explicitly set by the
  27. 13 Jan, 2016 1 commit
  28. 23 Nov, 2015 1 commit