1. 23 May, 2022 1 commit
  2. 23 Apr, 2022 1 commit
  3. 08 Apr, 2022 1 commit
  4. 30 Mar, 2022 1 commit
  5. 24 Mar, 2022 1 commit
  6. 23 Mar, 2022 2 commits
  7. 19 Mar, 2022 3 commits
  8. 18 Mar, 2022 1 commit
    • Carlos Garnacho's avatar
      keyboard: "Migrate" gtk-im-context setting before giving control to user · c8981ef0
      Carlos Garnacho authored
      This setting used to be modified by gsd-keyboard at runtime, but it no
      longer does. We want to leave this setting in a pristine state before
      we lend control to the user in order to avoid setting leftovers make
      GTK and others use the unintended IM module.
      
      Since the setting is actually staying on the same schema/path, there is
      no nice mechanism that would help us in doing a one-time port, so rely
      on a file at ~/.cache to make this happen once. In the common case, it
      just adds one stat() more at startup.
      
      After this migration is done, the gtk-im-module setting can be considered
      in full control of the user.
      c8981ef0
  9. 17 Mar, 2022 1 commit
  10. 14 Mar, 2022 1 commit
  11. 09 Mar, 2022 2 commits
  12. 06 Mar, 2022 1 commit
  13. 04 Mar, 2022 1 commit
  14. 14 Feb, 2022 2 commits
    • Carlos Garnacho's avatar
      Release 42.beta · 3240f5a5
      Carlos Garnacho authored
      3240f5a5
    • Carlos Garnacho's avatar
      xsettings: Adopt code to look up GTK IM module · e2d268eb
      Carlos Garnacho authored
      Right now, gsd-keyboard and gsd-xsettings have a strange relation
      where the first sets the gtk-im-module dconf setting for the latter
      to read the setting and forward it through XSettings.
      
      Since this detection is highly X11 specific, make it happen in the
      Xsettings daemon itself, from the relevant setting and device presence.
      
      This makes users still able to shoot themselves in the foot by changing
      the setting, X11 clients able to be told to switch to ibus if it turns
      out necessary, and Wayland clients unaffected otherwise.
      
      Related: gtk#4443
      e2d268eb
  15. 13 Feb, 2022 1 commit
  16. 12 Feb, 2022 2 commits
  17. 10 Feb, 2022 15 commits
  18. 08 Feb, 2022 1 commit
  19. 10 Jan, 2022 1 commit
  20. 04 Jan, 2022 1 commit
    • Florian Müllner's avatar
      xsettings: Support new "high-contrast" setting · c63419ef
      Florian Müllner authored
       We now have a boolean setting that determines whether the high-contrast
      theme should be used. Support it by automatically setting the existing
      `gtk-theme-name` and `gtk-icon-theme-name` properties when enabled.
      
      With that, it is no longer necessary to change the regular theme settings
      for high-contrast, so toggling between high-contrast and a non-default
      theme finally works reliably.
      c63419ef