1. 24 Jun, 2018 2 commits
  2. 23 Jun, 2018 2 commits
    • Jehan's avatar
    • Christian Hergert's avatar
      build: use xml-stripblanks with .ui resources · f05865ad
      Christian Hergert authored
      This adds a preprocess step to the .ui files to strip them of blank
      characters. It also removes the compressed='true' from the .ui files since
      that involves creating lots of decompressor objects when creating widgets.
      Doing so has runtime overhead and slows down the creation of initial
      application windows.
      The .ui files are left compressed for the Inspector, since that is not in
      the core performance path of application startup.
  3. 21 Jun, 2018 1 commit
  4. 20 Jun, 2018 11 commits
  5. 19 Jun, 2018 7 commits
  6. 18 Jun, 2018 2 commits
    • Matthias Clasen's avatar
      Merge branch 'window-activate-grab-3-again-24' into 'gtk-3-24' · a0b0cbe9
      Matthias Clasen authored
      gdk: activate surface on keyboard grabs
      See merge request GNOME/gtk!176
    • Samuel Thibault's avatar
      gdk: activate surface on keyboard grabs · f23bfc6b
      Samuel Thibault authored
      In 01455399e83a ("gdk: do not deactivate surface on keyboard grabs"), we
      made gdk avoid deactivating surfaces when another application takes a
      keyboard grab, by using has_focus_window instead of has_focus. That however
      broke activating surfaces when the gdk application acquired a grab itself,
      in which case has_focus_window is false but has_focus is true.
      We thus actually need to use both: surfaces should be activated either
      because we have normal keyboard focus, or because we grabbed the keyboard.
      This also renames HAS_FOCUS to APPEARS_FOCUSED to better reflect its
      Fixes #85
      (cherry picked from commit 3287ac96e02ff236d74db10164c5b0c1e7b2b0bf)
  7. 16 Jun, 2018 1 commit
  8. 12 Jun, 2018 1 commit
    • Michael Natterer's avatar
      gtk: fix wheel scrolling for very small adjustment page_size · c0ba041c
      Michael Natterer authored
      For very small page sizes of < 1.0, the effect of pow() is the
      opposite of what's intended and the scroll steps become unusably
      large, make sure we never get a scroll_unit larger than page_size /
      2.0, which used to be the default before the pow() magic was
  9. 11 Jun, 2018 1 commit
  10. 10 Jun, 2018 1 commit
  11. 08 Jun, 2018 1 commit
  12. 07 Jun, 2018 4 commits
  13. 06 Jun, 2018 3 commits
  14. 05 Jun, 2018 3 commits
    • Matthias Clasen's avatar
      Merge branch... · 7e0b9704
      Matthias Clasen authored
      Merge branch '1088-getting-css-properties-defined-in-em-etc-in-px-rounds-toward-0-delivering-1-too-few-pixels' into 'gtk-3-24'
      Resolve "Getting CSS properties defined in em (etc.) in px rounds toward 0, delivering 1 too few pixels"
      See merge request GNOME/gtk!158
    • Daniel Boles's avatar
      CssGadget: Round px values up for min-width|height · daecee75
      Daniel Boles authored
      Otherwise, requesting a min size in em where the equivalent in px had a
      fractional part would lead to the gadget getting allocated 1 too few px.
      You could see this in the CSS property vs. allocation in the Inspector.
      Note that margin/border/padding are left alone: the rationale is that we
      do as browsers do, and Benjamin said we already do that for those,
      whereas his tests on min-(width|height) showed otherwise.  My subsequent
      analysis indicated it to be far less clear-cut than that, but he remains
      unconvinced that we should ceil() all the things! So just do these ones.
    • Matthias Clasen's avatar
      docs: Add indices for 3.24 api · 700d167b
      Matthias Clasen authored
      We have some now.