1. 02 Aug, 2021 2 commits
  2. 31 Jul, 2021 2 commits
  3. 30 Jul, 2021 2 commits
    • Florian Müllner's avatar
      checkbutton: Activate when moving focus · 1728aa58
      Florian Müllner authored
      Currently we update the :active property on both the previous and
      new focus button. That "visually activate" the button and will
      emit ::toggled, but if the button is associated with an action,
      the action state won't change.
      
      Fix that by activating the new focus instead of explicitly fiddling
      with the :active property.
      1728aa58
    • Florian Müllner's avatar
      checkbutton: Delegate ::activate to the helper if appropriate · c50475de
      Florian Müllner authored
      If the button is associated with an action, the action is currently
      only activated when the button is clicked, not when it is activated.
      c50475de
  4. 29 Jul, 2021 3 commits
  5. 28 Jul, 2021 1 commit
  6. 27 Jul, 2021 2 commits
  7. 24 Jul, 2021 6 commits
  8. 23 Jul, 2021 1 commit
    • Alexander Mikhaylenko's avatar
      text: Use the widget y coordinate for gestures · 00cc9981
      Alexander Mikhaylenko authored
      Currently we use layout coordinates and widget height when determining
      where a click or drag has happened. If the widget has top padding (which it
      does inside a GtkEntry, for example), the area where it's possible to select
      text is shifted down, so the part of GtkText above the layout is not counted
      as the draggable area and instead the equal area below the widget is counted.
      
      Since GtkText is always single-line, there's no need to do any of that and
      we can use widget coordinates. Then the draggable area matches the widget
      and the problems goes away.
      00cc9981
  9. 22 Jul, 2021 4 commits
  10. 20 Jul, 2021 4 commits
  11. 16 Jul, 2021 2 commits
  12. 15 Jul, 2021 5 commits
  13. 14 Jul, 2021 6 commits
    • Matthias Clasen's avatar
      imcontext: Improve the docs · 4390f810
      Matthias Clasen authored
      Add more details about supported input methods.
      4390f810
    • Matthias Clasen's avatar
      imcontext: Simplify checking compose seqs · 92129a20
      Matthias Clasen authored
      Add the builtin table to the list of tables, and
      remove the duplicated code that checks builtin
      sequences separately.
      92129a20
    • Matthias Clasen's avatar
      composetable: Drop GtkComposeTableCompact · 54dffa07
      Matthias Clasen authored
      All tables use the compact format now, and we generate
      caches in that format too. Bump the cache version to 3
      for this.
      
      Replace the python script for generating the builtin table
      by a small C program using the same code to generate the data
      for the builtin table. This drops the restriction on only
      generating a single character in the builtin sequences.
      54dffa07
    • Matthias Clasen's avatar
      composetable: Ignore length 1 sequences · 1cff4bb2
      Matthias Clasen authored
      It turns out that the X11 Compose file has some
      length 1 sequences which are not interesting to us.
      1cff4bb2
    • Matthias Clasen's avatar
      imcontext: Replace the builtin sequences · 80872504
      Matthias Clasen authored
      When we find a Compose file, replace the builtin
      sequences with the table we found. This matches the
      semantics described in Compose(5), and makes it possible
      to drop unwanted sequences from the builtin table.
      
      It is slight change of behavior for users with existing
      Compose files. To match the previous behavior, you have
      to add
      
      include "%L"
      
      to your Compose file, to keep the builtin sequences in
      addition to your own.
      80872504
    • Matthias Clasen's avatar
      composetable: Allow removing sequences · 485dc052
      Matthias Clasen authored
      Interpret an empty string as value in the Compose
      file to mean: Remove this sequence.
      
      Tests included.
      485dc052