1. 23 Oct, 2018 3 commits
  2. 22 Oct, 2018 3 commits
  3. 21 Oct, 2018 3 commits
  4. 20 Oct, 2018 7 commits
  5. 19 Oct, 2018 4 commits
    • Jehan's avatar
      Issue #1924: Tool options mysteriously lock up due to DND/quartz issues. · 6b1ff0dd
      Jehan authored
      On macOS, the "drag-end" signal does not seem to be emitted in some
      cases, which leaves dockables in an unsensitive state. Rather than
      trying to fix GTK+2 which is half-maintained nowadays anyway, let's drop
      the unsensitivity. As a comment notes, this was anyway only a visual
      cue. Dragging dockables in GIMP 2.10 already shows a lot of other visual
      cues, so this is redundant.
      In case of drop failure, we also had to cleanup the icon widget and
      detach the dockable. This can be handled by the "drag-failed" (which
      hopefully work better on macOS).
      As an additional improvement, I raise the newly created dockable window,
      since this is the most likely behavior when you just detached a dock
      (and I realize it usually appeared behind other GIMP windows, at least
      on GNOME).
      Note: this is a gimp-2-10 only fix as master relies on GtkNotebook DnD
      code which (hopefully, as I haven't tested) doesn't have this issue. The
      detached window behind other windows issue doesn't exist on master, at
      the very least.
    • Ell's avatar
      tools: in performance-log-viewer.py, visualize percentage in profile viewer · 54dc7319
      Ell authored
      In the performance-log viewer's profile view, displasy in-line bar-
      chart-like visualization of function and source-line sample
      percentages, as part of the corresponding tree-view cells.
      (cherry picked from commit 26ea3348)
    • Marco Ciampa's avatar
      Small fix in Italian translation · c36b1d05
      Marco Ciampa authored
    • Josef Ridky's avatar
      Issue #2087 - Issues discovered by coverity scan · 56c8f832
      Josef Ridky authored
      Add missing fclose invocations and fix copy-paste issue.
      This issues has been discovered by coverity scan proceeded by Red Hat.
      Fixed some mistakes in the patch and added more fclose() (Mitch)
  6. 18 Oct, 2018 5 commits
  7. 17 Oct, 2018 1 commit
  8. 16 Oct, 2018 3 commits
  9. 15 Oct, 2018 1 commit
  10. 14 Oct, 2018 1 commit
  11. 13 Oct, 2018 1 commit
  12. 12 Oct, 2018 1 commit
  13. 11 Oct, 2018 4 commits
    • Alan01's avatar
      Updated Danish translation · e8f3751a
      Alan01 authored
    • Ell's avatar
      tools: fix performance-log viewer profile thread-filter · 65131b2c
      Ell authored
      In performance-log-viewer.py, fix thread-state toggling in the
      profile-view thread-filter popover, when not all threads are
      included in the current selection.
      (cherry picked from commit 43b492ff)
    • Ell's avatar
      app: always use libunwind for symbol names in GimpBacktrace Linux backend · b1cba6b1
      Ell authored
      In the GimpBacktrace Linux backend, always use libunwind, when
      available, to find symbol names, even if dladdr() or libbacktrace
      had already found one.  libunwind provides more descriptive names
      in certain cases, and, in particular, full symbol names for C++
      Note that, in some cases, this can result in a discrepancy between
      the reported symbol name, and the corresponding source location.
      (cherry picked from commit 72fc0174)
    • Ell's avatar
      app: fix gimp_wait() deadlock · 397bbb29
      Ell authored
      In the GUI implementation of gimp_wait(), explicitly finish the
      input-pipe async operation after the busy-dialog plug-in
      terminates, to avoid the async callback function from being
      repeatedly called, stalling the main thread.  Previously, this code
      relied on gimp-parallel implicitly aborting the async operation,
      but this is no longer the case since commit
      (cherry picked from commit 85b16b9e)
  14. 10 Oct, 2018 3 commits
    • Ell's avatar
      tools: add performance-log-coalesce.py; use in performance-log-viewer · 8c91206d
      Ell authored
      Add a new performance-log-coalesce.py tool, which groups together
      performance-log address-map entries belonging to the same function
      into a single symbol, by filling-in missing base symbol addresses.
      The addresses are grouped such that each set of addresses
      corresponding to a symbol of the same name, in the same source
      file, are given the same (unique, but arbitrary) base address.
      See the previous commit for why this is necessary.
      This should work fine in most cases, however, for logs produced on
      Windows, it can over-coalesce addresses belonging to different C++
      lambda-functions in the same source file, since they all seem to be
      given the same _FUN symbol name.
      Use the new tool as part of the pipeline in performance-log-viewer.
      (cherry picked from commit cb51ea98)
    • Snehalata Shirude's avatar
      Update Marathi translation · f314bbd5
      Snehalata Shirude authored
    • Ell's avatar
      app: in GimpBacktrace Windows backend, avoid bogus symbol addresses · d0fdff71
      Ell authored
      In the GimpBacktrace Windows backend, avoid reporting meaningless
      symbol addresses when failing to retrieve meaningful ones.
      Unfortunately, it seems that we never get symbol addresses for
      symbols that have debug information, which negatively affects the
      log viewer's call graph.  We're going to have to work around this.
      (cherry picked from commit 52772cf3)