1. 28 Sep, 2019 1 commit
    • Ell's avatar
      app: update image bounding box when moving layer inside/outside of group · 2a753170
      Ell authored
      In GimpImage, update the image's bounding box in response to the
      layer container's "add" and "remove" signals, instead of during
      gimp_image_{add,remove}_layer(), so that the bounding box is
      properly updated when moving an existing layer inside/outside of a
      layer group, instead of only when adding/removing a new layer.
      
      Even though moving a layer across group boundary doesn't change the
      overall image bounding box, it does change the group's bounding
      box, affecting the image bounding box.  It's therefore necessary to
      update the image bounding box again when the layer is re-added to
      the layer stack, so that the bounding box doesn't get stuck in an
      intermediate state.
      2a753170
  2. 27 Sep, 2019 4 commits
  3. 26 Sep, 2019 9 commits
    • Jehan's avatar
      Issue #3990: make the status of the XCF docs a bit clearer (hopefully). · 80e2e0a5
      Jehan authored
      Though it may have started as an unofficial document, it is clearly now
      an official one (which should be obvious since it is in our source
      repository, but apparently some people get misled by the historical
      "Status" text to think this to be somehow unofficial).
      So first of all, change the s/official/unofficial/ mention.
      
      Secondly, add a small paragraph explicitly telling that the document is
      complete (and meant to be), to the best of our knowledge. This document
      is a detailed, full and exhaustive written "specification" of the XCF
      format up to GIMP 2.10.x (even though the normative spec is still the
      code itself). Now we are humans, we may have missed something, and if
      so, this is just to be considered as any other bug, and reported to us
      nicely to be fixed.
      80e2e0a5
    • Jordi Mas's avatar
      Update Catalan translation · ab16f001
      Jordi Mas authored
      ab16f001
    • Martin Srebotnjak's avatar
      Updated Slovenian translation · eb070343
      Martin Srebotnjak authored
      eb070343
    • Martin Srebotnjak's avatar
      Updated Slovenian translation · 5c966343
      Martin Srebotnjak authored
      5c966343
    • Martin Srebotnjak's avatar
      Updated Slovenian translation · 8829a728
      Martin Srebotnjak authored
      8829a728
    • Martin Srebotnjak's avatar
      Updated Slovenian translation · 44ad1a67
      Martin Srebotnjak authored
      44ad1a67
    • Martin Srebotnjak's avatar
      Updated Slovenian translation · 2ea77e87
      Martin Srebotnjak authored
      2ea77e87
    • Michael Natterer's avatar
      libgimp: improve handling of procedure default values a lot · 45e96a0f
      Michael Natterer authored
      Add internal GimpProcedureConfig API to load/save "default values"
      which are to be treated as if they were the hardcoded GParamSpec
      defaults, but user-configurable. Also make all other load/save
      functions available to other libgimp files.
      
      In gimp_procedure_run(), if incomplete arguments are passed, don't
      just complete them with the GParamSpec defaults, but look up the
      user-saved defaults and use them if they exist. This happens before
      everything else and brings back the PNG export feature of using
      user-saved defaults also in non-interactive mode (but for all
      procedures not just PNG export).
      
      In GimpProcedureDialog, add "Load Defaults" and "Save Defaults"
      buttons, they are the only way of managing the user-configurable
      procedure defaults.
      
      When clicking "Reset", show a popover with the reset options "Initial
      Values" and "Factory Defaults".
      45e96a0f
    • Michael Natterer's avatar
      e4acb969
  4. 25 Sep, 2019 8 commits
  5. 24 Sep, 2019 8 commits
  6. 23 Sep, 2019 10 commits