1. 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
  2. 23 Mar, 2017 1 commit
  3. 19 May, 2016 1 commit
  4. 13 Jul, 2015 2 commits
  5. 20 Oct, 2014 1 commit
    • Michael Natterer's avatar
      Bug 736907 - Compat mode for XCF · 950f753e
      Michael Natterer authored
      - add gimp_image_get,get_xcf_compat_mode()
      - add a compat toggle to GimpFileDialog which is shown and sensitive
        only for a save (not export), and if the image structure allows
        to save an old version at all. The button also has a tooltip
        which explains why it is sensitive and what it does
      - add "gboolean xcf_compat" to file_save_dialog_save_image()
      - in file_save_dialog_save_image(), call image_set_xcf_compat_mode(TRUE)
        only around the call to file_save() and set it to FALSE after saving
      - in xcf_save_invoker(), honor the image's XCF compat flag and save an
        RLE-compressed XCF if possible
      
      The above is very convoluted and doesn't pass the "xcf_compat" boolean
      directly because we can't change the parameters of gimp-xcf-save, and
      because the gimp-xcf-save might be called indirectly.
      950f753e
  6. 27 Sep, 2014 1 commit
  7. 25 Aug, 2014 1 commit
  8. 07 Jul, 2014 2 commits
  9. 02 Jul, 2014 1 commit
  10. 15 Jun, 2014 1 commit
  11. 21 Mar, 2014 1 commit
  12. 23 Jun, 2013 1 commit
    • Michael Natterer's avatar
      Add support for both gamma-corrected and linear for all bit depths · caf73f5f
      Michael Natterer authored
      - Add new enum GimpComponentType which contains u8, u16, u32 etc.
      - Change GimpPrecision to be u8-linear, u8-gamma, u16-linear etc.
      - Add all the needed formats to gimp-babl.c
      - Bump the XCF version to 5 and make sure version 4 with the old
        GimpPrecision enum values is loaded correctly
      
      This change blows up the precision enums in "New Image" and
      Image->Precision so we can test all this stuff. It is undecided what
      format will be user-visible options in 2.10.
      caf73f5f
  13. 06 Oct, 2012 1 commit
  14. 17 Jul, 2012 1 commit
    • Michael Natterer's avatar
      Bug 676566 - Window title becomes "Untitled" after exporting without saving · 220b2867
      Michael Natterer authored
      Fix this and other issues more globally by moving the logic that
      formats the image's display name into the GimpImage object, and return
      the properly formatted name, e.g. "Foo.xcf", or "[Foo] (imported)"
      from gimp_image_get_display_name().
      
      Also add gimp_image_get_display_path() which returns the full path
      instead. Use the two functions for formatting the image title, and
      apply various other fixes that make sure the UI always uses the same
      string to identify the image.
      
      Call gimp_object_name_changed() whenever the save/export status
      changes, so the image's cached display name and path get cleared.
      220b2867
  15. 18 May, 2012 1 commit
  16. 07 May, 2012 2 commits
  17. 02 May, 2012 18 commits
  18. 12 Aug, 2011 1 commit
  19. 02 Feb, 2011 2 commits