1. 29 Sep, 2018 10 commits
    • Ell's avatar
      app: don't commit trivial warp transform · 9b3c2e9b
      Ell authored
      In the warp tool, don't commit a trivial (empty) transform.  This
      is especially important now that exiting the tool through undo
      causes it to get comitted (... with a trivial transform).
      (cherry picked from commit d12dd3fb)
    • Ell's avatar
      Issue #1180 - Warp tool aborts changes to layer A when ... · 943757c1
      Ell authored
      ... changing layers and warping layer B
      Add a new GimpToolControl::dirty_action field, which specifies the
      tool action to perform when the a dirty event matching the tool
      control's dirty mask occurs; this field defaults to HALT.  Apply
      this action to the active tool in tool-manager in response to a
      matching dirty event, instead of unconditionally halting the tool.
      Likewise, use this action to stop the active tool in response to a
      button-press event on a different drawable in the same image.
      Set the dirty action of the gradient and warp tools to COMMIT, so
      that they get comitted, rather than stopped, in cases such as
      switching layers (including switching to/from quick-mask mode),
      and, for the warp tool, changing the selection.
      (cherry picked from commit ed20393f)
    • Alan01's avatar
      Updated Danish translation of gimp-windows-installer · 498c3f5b
      Alan01 authored and Ask Hjorth Larsen's avatar Ask Hjorth Larsen committed
    • Alan01's avatar
      Updated Danish translation of gimp-plug-ins · 2ce208c0
      Alan01 authored and Ask Hjorth Larsen's avatar Ask Hjorth Larsen committed
    • Alan01's avatar
      Updated Danish translation of gimp-libgimp · 66acf664
      Alan01 authored and Ask Hjorth Larsen's avatar Ask Hjorth Larsen committed
    • Alan01's avatar
      Updated Danish translation · e98dbc3d
      Alan01 authored and Ask Hjorth Larsen's avatar Ask Hjorth Larsen committed
    • Ell's avatar
      app: avoid applying buffer to drawable if application region is empty · 2e47f827
      Ell authored
      In gimp_drawable_real_{apply,replace}_buffer(), bail if the
      applcation region, after intersection with the drawable and mask
      extents, is empty.  This avoids trying to create a GeglBuffer with
      negative width/height.
      (cherry picked from commit ae3c0062)
    • Ell's avatar
      Issue #2287 - Weird things happen with dodge tool ... · fce08d2a
      Ell authored
      ... (some sort of corruption)
      In gimp_drawable_real_replace_buffer(), adjust the processed buffer
      and mask_buffer regions according to the changes made to the
      application region, as calculated by intersecting it with the
      drawable and mask extents.  This fixes wrong application position
      when painting using the heal, dodge/burn, smudge, or convolve
      tools, on a drawable whose origin is above/to the left of the
      image's origin, and there's a selection active.
      (cherry picked from commit a782acab)
    • Ell's avatar
      Issue #2222 - Warp Transform doesn't commit changes upon saving ... · 943f92a6
      Ell authored
      ... the XCF file
      Add a "saving" signal to GimpImage, which is emitted when the image
      is about to be saved or exported (but before it's actually saved/
      exported).  Connect to this signal in tool-manager, and commit the
      current tool in response (unless its GimpToolControl::preserve is
      (cherry picked from commit ae628a86)
    • Ell's avatar
      tools: in performance-log-viewer.py, retain call-graph path · df265073
      Ell authored
      In the performance-log viewer's profile view, retain the current
      call-graph path across state changes.
      (cherry picked from commit fca05065)
  2. 28 Sep, 2018 3 commits
  3. 27 Sep, 2018 4 commits
    • Piotr Drąg's avatar
      Update Polish translation · f5598dc7
      Piotr Drąg authored
    • Jehan's avatar
      desktop: prepare release of GIMP 2.10.8. · e7365326
      Jehan authored
      Please everyone, feel free to update the list of upcoming
      changes/features, if you feel some particular change should be more
      prominently exposed in this list (or at the opposite that some change is
      not worth mentionning), or for rewording, etc.
      (cherry picked from commit ba53a833)
    • Ell's avatar
      app: construct tool-options GUI lazily · c9510721
      Ell authored
      We currently construct the tool-options GUI for all the tools at
      startup, which takes a significant amount of time.  Instead,
      only register the GUI construction function with the tool-options
      object, using the new gimp_tools_set_tool_options_gui_func()
      function, and use the registered function to construct the GUI when
      actually needed.
      (cherry picked from commit c1347a7f)
    • Ell's avatar
      tools: various improvements in gimp-performance-log-viewer.py · 6bc2b330
      Ell authored
      Fix int-ratio variable formatting when the input is NaN, which can
      happen when calculating the standard deviation, if all the values
      are infinite.
      Fix keyboard sample-range selection.
      Deselect all samples when right-clicking a sample graph.
      (cherry picked from commit d33fb0e7)
  4. 26 Sep, 2018 5 commits
    • Ell's avatar
      plug-ins: in script-fu, don't query PDB procedures' info on startup · 97a29b1e
      Ell authored
      script-fu used to query the information of every PDB procedure on
      startup, in order to get the number of parameters for each
      procedure.  This was done so that nullary procedures were defined
      in such a way as to accept (and ignore) any number of arguments
      (and at least one of the scripts we ship relies on this behavior).
      However, this requires expensive back-and-forth communication with
      the main GIMP process, which notable slowed down script-fu's
      startup, and had a non-negligible impact on GIMP's startup time.
      Instead, avoid querying procedure information, and implement the
      special behavior for nullary procedures at call time.  We do this
      by defining, in addition to the "strict" gimp-proc-db-call
      procedure, a "permissive" -gimp-proc-db-call internal procedure,
      and using the latter to call the predefined PDB procedures.
      (cherry picked from commit 9a2999a5)
    • Rafael Fontenelle's avatar
    • Rafael Fontenelle's avatar
    • Marco Ciampa's avatar
      Updated Italian translation · 35bf5bca
      Marco Ciampa authored
    • Ell's avatar
      Issue #2272 - Crash when using the intelligent-scissors tool ... · 49390462
      Ell authored
      ... after erasing all points
      When erasing the last remaining point in the iscissors tool, halt
      the tool, rather than leaving the tool active with an empty curve,
      which it is not prepared to handle, and which results in a segfault
      once trying to add a new point.
      Additionally, when erasing the last remaining segment (i.e., the
      two last remaining points), don't erase the entire segment (i.e.,
      both points), but rather convert the segment to its initial point,
      so that, in effect, we only erase the last point of the segment.
      (cherry picked from commit a5baba55)
  5. 25 Sep, 2018 4 commits
  6. 23 Sep, 2018 9 commits
  7. 21 Sep, 2018 4 commits
  8. 20 Sep, 2018 1 commit