1. 21 Dec, 2017 1 commit
  2. 20 Dec, 2017 4 commits
  3. 02 Dec, 2017 1 commit
  4. 29 Nov, 2017 1 commit
  5. 28 Nov, 2017 1 commit
  6. 29 Oct, 2017 1 commit
  7. 25 Oct, 2017 1 commit
  8. 24 Oct, 2017 1 commit
  9. 23 Oct, 2017 1 commit
  10. 17 Oct, 2017 4 commits
    • Piotr Drąg's avatar
      Update Polish translation · 3d3a8475
      Piotr Drąg authored
      3d3a8475
    • Ell's avatar
      Bug 683553 - Spinscale scrollvalues in Brushsize are much too small · b2f48cd3
      Ell authored
      Increase the step and page increments of the brush radius spinscale
      in the brush editor to 1.0 and 10.0, respectively, to match those of
      the corresponding spinscale in the paint tool options.
      
      (cherry picked from commit 5456ddbb)
      b2f48cd3
    • Piotr Drąg's avatar
      desktop: fix keywords · db7d6cb3
      Piotr Drąg authored
      The semicolons should be used instead of spaces if we want
      it to work and validate.
      
      Also adds a translator comment to avoid broken translations.
      
      (cherry picked from commit 1f9451b8)
      db7d6cb3
    • Jehan's avatar
      desktop: add "GIMP" in keywords to fix search with flatpak. · c4ebfc84
      Jehan authored
      The only reason "gimp" can be used to search for the software (for
      instance in GNOME overview) is because it is the Exec (the short name
      is written neither in the Name nor Comment sections). When packaged by
      systems like flatpak, this key is changed to `flatpak run ...` and
      searching "gimp" does not even return the software!
      Adding a Keywords entry to our desktop file fixes this.
      
      Apart from "gimp", I take the opportunity to add other relevant keywords
      from our website which currently would not display GIMP as a result:
      graphic design illustration painting.
      
      (cherry picked from commit 472608fe)
      c4ebfc84
  11. 05 Oct, 2017 2 commits
    • Ell's avatar
      Bug 788461 - Selection with a Fixed size is created with an ... · ac0719f9
      Ell authored
      ... off-by one size in special cases
      
      The last commit wasn't drastic enough.  We changed SIGNED_ROUND()
      to use RINT(), which, in turn, may use rint().  However, rint()
      effectively breaks ties to even, so that we get stuff like
      'rint (1.5) - rint (0.5) == 2.0 - 0.0 == 2.0'.  This can't be
      good--it's entirely possible that we're bitten by this in other
      cases without noticing.
      
      Avoid rint() entirely in RINT(), and always use 'floor (x) + 0.5'
      instead, which always breaks ties up.  Hopefully, this doesn't
      break anything else...
      
      (cherry picked from commit 80a52686)
      ac0719f9
    • Ell's avatar
      Bug 788461 - Selection with a Fixed size is created with an ... · eadd42b9
      Ell authored
      ... off-by one size in special cases
      
      SIGNED_ROUND(), which is used by GimpToolRectangle, among other
      things, used to round negative values which lie exactly between
      two integers, i.e., -foo.5, down.  This could lead to the rectangle
      being one pixel bigger than expected, in either dimension, when one
      of its edges had a negative coordinate, and the opposite edge had a
      positive coordinate.
      
      Fix SIGNED_ROUND() to always round such values up, regardless of
      sign.
      
      (cherry picked from commit e8b37a7a)
      eadd42b9
  12. 21 Sep, 2017 1 commit
  13. 05 Sep, 2017 1 commit
  14. 28 Aug, 2017 2 commits
    • Ell's avatar
      */Makefile.am: work around a bug in the new glib-genmarshal · 32eb0831
      Ell authored
      glib-genmarshal was rewritten in glib 2.53.4, and as of now (2.53.6)
      it has a bug where it unconditionally generates marshaler bodies,
      even for standard marshalers, even with --stdinc.  This causes
      libgimpwidgets to define and export g_cclosure_marshal_VOID__INT()
      and g_cclosure_marshal_VOID__OBJECT(), which upsets defcheck, and
      breaks the build.
      
      Work around this for now by using --header --body when generating
      the marshal.c files, which includes the prototypes in the source,
      instead of including the header ourselves.  This is the only code
      path where the new glib-genmarshal doesn't generate bodies for
      standard marshalers.  Note, however, that this usage is deprecated,
      so we'll probably want to change it back once it's fixed.
      
      (cherry picked from commit 0ef3795f)
      32eb0831
    • Ell's avatar
      Bug 785152 - The default GIMP brush should not be a clipboard brush · 4bfe4ea4
      Ell authored
      Fix the default brush name -- "Round Fuzzy" was gone for a while :P
      
      The fact that "Hardness 050" was the default brush regardless is a
      conincidence; see the bug report for more details.
      
      (cherry picked from commit 494d1894)
      4bfe4ea4
  15. 23 Aug, 2017 4 commits
  16. 09 Aug, 2017 1 commit
    • Ell's avatar
      libgimpwidgets: init GimpColorHexEntry's text after construction · 0eed2308
      Ell authored
      Initialize GimpColorHexEntry's text (to "000000") in constructed(),
      instead of init().  Otherwise, it gets cleared during construction,
      so that color entries set initially to black are empty.
      
      (cherry picked from commit 1e9898cb6bb623b3abd2ee503cc83d991243cb7e)
      0eed2308
  17. 31 Jul, 2017 1 commit
  18. 28 Jul, 2017 1 commit
    • Ell's avatar
      app: limit allowable tile data size in XCFs · d7a9e607
      Ell authored
      When loading tiles from an XCF, reject tiles whose on-disk size is
      greater than 1.5 times the size of an uncompressed tile -- a limit
      that is already present for the last tile in the buffer.  This
      should allow for the possibility of negative compression, while
      restricting placing a realistic limit.
      
      Currently, no limit is placed on the on-disk tile data size.  When
      loading RLE-compressed tiles, a buffer large enough to hold the
      entire on-disk tile data, up to 2GB, is allocated on the heap.  This
      allows a malicious XCF, which may be much smaller than 2GB, to cause
      a very large allocation, which may abort the program if there's not
      enough memory (or not enough address space, which is much more likely
      on 32-bit systems.)
      d7a9e607
  19. 25 Jul, 2017 1 commit
  20. 08 Jul, 2017 1 commit
  21. 07 Jul, 2017 3 commits
  22. 16 Jun, 2017 1 commit
    • Jehan's avatar
      plug-ins: properly "Apply layer masks before saving" when checked. · f54659dd
      Jehan authored
      The `if` test was inverted. When the option is checked, we don't want to
      add the GIMP_EXPORT_CAN_HANDLE_LAYER_MASKS capability so that
      gimp_export_image() applies the mask.
      This is a first step to fix bug 783528, but it's not finished. Right
      now, when the option is unchecked, the mask is simply ignored. We want
      to export a PDF mask instead.
      
      (cherry picked from commit 0bd94f17)
      f54659dd
  23. 07 Jun, 2017 1 commit
  24. 04 Jun, 2017 1 commit
  25. 22 May, 2017 2 commits
  26. 15 May, 2017 1 commit