1. 18 Apr, 2018 1 commit
  2. 11 Jan, 2018 1 commit
    • Jehan's avatar
      plug-ins: file export should follow preferences regarding metadata. · 82f6baf2
      Jehan authored
      Various plug-ins exporting metadata should now follow preferences, which
      would override any default. Of course these preferences can still be
      overriden by saved settings (global parasite), previous run settings,
      and finally through the GUI when interactive.
      82f6baf2
  3. 10 Jan, 2018 1 commit
    • Jehan's avatar
      Bug 790552 - do not save metadata by default. · 096debb0
      Jehan authored
      This is a privacy concern. Whereas importing metadata is usually a good
      idea, exporting it should be a conscious action. A lot of private data
      can be leaked through metadata and many people don't realize it (which
      also usually means they don't need it). On the other hand, the people
      who realize it are the ones who would explicitly edit the metadata and
      check what they want to be exported or not.
      
      This is only a first step. Some people may want to always export the
      metadata and for these people, there should be abilities to change the
      default.
      096debb0
  4. 21 Aug, 2017 1 commit
    • Michael Natterer's avatar
      Move the new "default_new_layer_mode" APIs to the image... · e16c8a23
      Michael Natterer authored
      ...in both the core and libgimp.
      
      Images now know what the default mode for new layers is:
      
      - NORMAL for empty images
      - NORMAL for images with any non-legacy layer
      - NORMAL_LEGAVY for images with only legacy layers
      
      This changes behavior when layers are created from the UI, but *also*
      when created by plug-ins (yes there is a compat issue here):
      
      - Most (all?) single-layer file importers now create NORMAL layers
      - Screenshot, Webpage etc also create NORMAL layers
      
      Scripts that create images from scratch (logos etc) should not be
      affected because they usually have NORMAL_LEGACY hardcoded.
      
      3rd party plug-ins and scripts will also behave old-style unless they
      get ported to gimp_image_get_default_new_layer_mode().
      e16c8a23
  5. 20 Aug, 2017 1 commit
  6. 26 Feb, 2017 1 commit
  7. 12 Feb, 2017 1 commit
  8. 30 Jan, 2017 1 commit
  9. 08 Jan, 2017 1 commit
  10. 03 Jan, 2017 2 commits
  11. 08 Nov, 2016 1 commit
  12. 23 Jul, 2016 3 commits
  13. 25 Jun, 2016 1 commit
    • Richard Kreckel's avatar
      Bug 768044 - Fix many typos · dd9b0fc5
      Richard Kreckel authored
      This fixes many typos in comments and one in a user-visible string (msgid
      "center abscisse" changed to "center abscissa" in affected po files. too).
      dd9b0fc5
  14. 01 May, 2016 1 commit
  15. 21 Apr, 2016 1 commit
    • Massimo Valentini's avatar
      Bug 765336: CRITICAL warning loading a thumbnail-less... · 5e5fb777
      Massimo Valentini authored
      tiff GIMP saved
      
      the plugin unconditionally used to add a TIFFTAG_SUBIFD
      whose number_of_sub_IFDs was wrong when the user asked
      not to include a thumbnail.
      
      Reloading the file in GIMP resulted in:
      
      ** (file-tiff:1): CRITICAL **: Directory SubImage1 with 18761 entries considered invalid; not read.
      5e5fb777
  16. 19 Apr, 2016 2 commits
  17. 16 Feb, 2016 1 commit
  18. 29 Dec, 2015 2 commits
  19. 05 Dec, 2015 1 commit
  20. 02 Dec, 2015 1 commit