1. 09 Aug, 2018 7 commits
  2. 08 Aug, 2018 3 commits
  3. 07 Aug, 2018 7 commits
  4. 06 Aug, 2018 8 commits
  5. 05 Aug, 2018 3 commits
  6. 04 Aug, 2018 5 commits
    • Jehan's avatar
      Issue #1974: Memory leak in gimpimage.c. · 71f37d41
      Jehan authored
      Ok my previous fix was wrong (at least for the part in the macro). This
      is a macro, not a function. So each time we write _reason, the call to
      g_strdup_printf() is reevaluated, hence data is allocated.
      The right fix is to prepend `tmp` to the list, not `_reason`.
      Thanks to Massimo for the debugging, as always!
      (cherry picked from commit 2912fe7c)
    • Jehan's avatar
      Issue #1974: Memory leak in gimpimage.c. · 8909684b
      Jehan authored
      ADD_REASON macro was leaking the allocated string when version_reason
      return value was NULL (i.e. when we didn't care about the version
      Also we were not properly freeing all the reason strings at the end,
      only the list. Use g_list_free_full() instead of g_list_free().
      (cherry picked from commit 0ab682b0)
    • Ell's avatar
      Issue #1846 - "gitlab::" typo in the Windows installer · 53b07a92
      Ell authored
      Introduced by commit 8eb77376.
      Change to "gitlab:".
      (cherry picked from commit aafa9259)
    • Ell's avatar
      app: short-circuit GimpProjection bounds-changed handler if disjoint · 0edbb058
      Ell authored
      In gimp_projection_projectable_bounds_changed(), bail early by
      calling gimp_projection_projectable_structure_changed() instead, if
      the new bounds don't intersect the old bounds.
      (cherry picked from commit c6b8a421)
    • Ell's avatar
      app: fix gimp_projection_projectable_bounds_changed() · 53afeb11
      Ell authored
      In gimp_projection_projectable_bounds_changed(), which is called by
      GimpProjection in response to a GimpProjectable::bounds-changed
      signal, invalidate all regions of the new projection that weren't
      copied from the old projection, so that they get rendered upon
      flushing, instead of remaining empty.
      Additionally, fix preview invalidation -- in particular, don't
      directly invalidate the projectable's preview, even if preview
      invalidation is already queued and chunk rendering was finished by
      the boundary change, and instead always queue a preview
      (cherry picked from commit bb5e3fd9)
  7. 03 Aug, 2018 7 commits
    • Pat David's avatar
      app, libgimpbase: update vertical text labels (shorten) · a1d2c05f
      Pat David authored
      Shortening vertical text option labels a little bit.
      (cherry picked from commit 0ce4db74)
    • Ell's avatar
      app: avoid re-rendering group layers upon resizing · d8c0368a
      Ell authored
      Make sure we don't unnecessarily update the group layer's drawable
      while flusing the group's projection during resizing, since we want
      to either update the entire drawable, or avoid any updates, when
      replacing the drawable's buffer.  Note that explicitly supressing
      updates in this case should theoretically not be necessary, but the
      fact that the call to gimp_projectable_bounds_changed() can result
      in reconstructing the projection (see the FIXME comment in that
      function) makes it necessary in some cases nonetheless.
      (cherry picked from commit bd726c96)
    • Ell's avatar
      app: avoid re-rendering group layers upon translation · 5eaa2f90
      Ell authored
      When translating group layers, there's no need to re-render the
      group's projection -- we can simply update the group's offset (and
      offset node) directly, and redirect any layer-stack "update"
      signals to the group's drawable.  This significantly improves
      performance when moving groups.
      (cherry picked from commit 3ff820a0)
    • Ell's avatar
      app: use gimp_projectable_bounds_changed() when resizing group layers · bcbc3c23
      Ell authored
      In GimpGroupLayer, use gimp_projectable_bounds_changed() when
      updating the group layer's size, instead of reconstructing the
      projection, unless reallocation of the projection has been
      requested.  This is more efficient, since it simply copies the
      content of the projection's old buffer to the new buffer, rather
      than re-rendering the graph.
      (cherry picked from commit 1bb3e962)
    • Ell's avatar
      app: stop idle projection rendering when flushing group layers · 379d65e0
      Ell authored
      In gimp_group_layer_flush(), stop any idle rendering, initiated
      when a new buffer is allocated, before flushing the group's
      pickable.  Otherwise, the idle rendering is finished synchronously,
      which unnecessarily introduces a noticeable lag.
      (cherry picked from commit a4957c7c)
    • Ell's avatar
      app: add "update" parameter to gimp_drawable_set_buffer_full() · adadd4bb
      Ell authored
      ... which specifies whether or not to update the drawable in
      response to the buffer change.
      Pass TRUE for "update" at all existing call sites, to keep the
      current behavior.
      (cherry picked from commit 26a8d141)
    • Ell's avatar
      app: respond to GimpProjectable::bounds-changed in GimpProjection · 09d50449
      Ell authored
      In GimpProjection, respond to the projectable's "bounds-changed"
      signal, by reallocating the buffer, and copying the corresponding
      region of the old buffer (using
      gimp_tile_handler_validate_buffer_copy(), added a few commits back,
      so that the relevant portion of the validate handler's dirty region
      is also copied).  Additionally, shift and clip all outstanding
      update regions as necessary (actually, we avoid copying the buffer
      when a shift is necessary, and simply reconstruct the projection;
      see FIXME comment in the code.)
      (cherry picked from commit fbeae361)