1. 02 Aug, 2020 1 commit
    • Ell's avatar
      app: add gimp_log_{set,remove}_handler() · a8e3f36e
      Ell authored
      ... which set/remove a GLIB log handler for all domains used by
      Use the new functions in errors.c, instead of using
      g_log_set_handler() directly.
      (cherry picked from commit a143bfdf)
  2. 30 Jul, 2020 1 commit
  3. 29 Jul, 2020 5 commits
    • Ell's avatar
      app: in GimpDashboard, fix progressive-performance-log env-var · 38b1298c
      Ell authored
      (cherry picked from commit d11cbbbb)
    • Ell's avatar
      app: add progressive performance logs · 60ca6110
      Ell authored
      Add an option to record progressive performance logs.  Progressive
      logs contain complete information after each recorded sample, by
      writing partial address maps at each sample, containing all new
      addresses introduced by the sample.  Furthermore, when recording a
      progressive log, the output stream is flushed after each sample.
      This allows recording complete logs even in cases where they can't
      be properly terminated, such as when GIMP crashes or freezes in the
      middle of the log.
      Progressive logs are disabled by default, since they potentially
      increase the sampling cost.  They can be enabled through a toggle
      in the log file-dialog, or through the
      GIMP_PERFORMANCE_LOG_PROGRESSIVE environment varaible.
      (cherry picked from commit 146c2343)
    • Ell's avatar
      app: allow controlling performance-log parameters through the UI · 7e21f792
      Ell authored
      When recording a performance log, allow setting the log parametrs
      through the file dialog.  Currently, this includes the sample
      frequency, and the option to include backtraces.
      These options are still controllable through the
      GIMP_PERFORMANCE_LOG_BACKTRACE environment variables.  When set,
      the variables override the values entered through the UI.
      (cherry picked from commit 126002c5)
    • Ell's avatar
      app: in GimpBacktrace Windows backend, return NULL backtrace if not initialized · 5fc30e59
      Ell authored
      In the Windows implementation of gimp_backtrace_new(), return NULL
      if the backend is not fully initialized.
      (cherry picked from commit 95b69dd7)
    • Ell's avatar
      Issue #5472 - CRITICAL while using Move tool with arrow keys · 22690aba
      Ell authored
      In gimp_edit_selection_tool_translate(), perform the active-item
      checks even when the effective translation offset is 0, and only
      bail afterwards.  This avoids erroneously calling
      gimp_tool_message_literal() with a NULL message in this case.
      (cherry picked from commit 3a462a5e)
  4. 28 Jul, 2020 1 commit
    • Ell's avatar
      Issue #4536 - Seg fault when trying to open image on Google Drive (Gnome 3.34.3) · c38a23b9
      Ell authored
      In file_open_image(), mount non-native files *before* looking up a
      file-proc.  Previously, we'd only mount the file after the initial
      lookup, and fail to perform a second lookup if the mount succeeded,
      leaving us with a NULL file-proc and a subsequent segfault.
      Additionally, simplify the rest of the remote-file code-path.
      (cherry picked from commit 0829dba9)
  5. 17 Jul, 2020 3 commits
    • Jehan's avatar
      app: show playground if any of the experimental feature is enabled. · a897b489
      Jehan authored
      Basically if you enabled OpenCL or any of the experimental tools, it
      will show the Playground in Preferences. Otherwise, say you enabled some
      experimental feature months ago (e.g. with the CLI option) and you now
      experience crashes or whatnot. And you forgot how to change it, and only
      remembered that there was something in Preferences. It would make you
      crazy to not find the tab again to disable the option.
      This is even more important as OpenCL is moving from a normal option to
      a playground option. So you might not even have ever seen the Playground
      tab in Preferences and would not know how to disable OpenCL after you
      enabled it originally in "System Resources" tab.
      So now Playground is visible with any of these 3 conditions:
      * If you use an unstable version.
      * If you run GIMP with --show-playground option.
      * If you previously enabled one of the playground options.
      (cherry picked from commit d3ef6cfb)
    • Jehan's avatar
      app: move OpenCL settings into the Playground. · ebb5c3c0
      Jehan authored
      After discussions on IRC, it was decided that our current level of
      support of OpenCL was not good enough. As a normal settings, people just
      see it as a normal acceleration checkbox, even despite the warning text
      and emoticone saying the opposite (i.e. it may even slow things down in
      some cases).
      Basically this feature needs more love to be back into mainstream
      (cherry picked from commit 0f806d0e)
    • Jehan's avatar
      app: add contents of /.flatpak-info in the verbose info. · a0c1a2cc
      Jehan authored
      This file is available in a flatpak sandbox and will contain various
      info such as the build commit, very useful info as we can have several
      builds for a same version. For instance if we have exactly the right
      commit, we can load exactly the same binary as a bug reporter very
      easily, hence are able to get source correspondance without necessarily
      asking reporters to install debug symbols (though it stays easier if
      they can do it).
      Other interesting info contained in this file are the exact runtime
      used, the installed application or runtime extensions, the permissions
      (people may override our flatpak permissions so it's useful to be able
      to check when they did) and environment variables…
      (cherry picked from commit bc5f6371)
  6. 09 Jul, 2020 1 commit
    • Jehan's avatar
      app: make "gegl:matting-levin" default engine of Foreground Select tool. · aeed6fcb
      Jehan authored
      Even though this engine is optional, we already have the code to detect
      its absence at runtime, and to fallback to "gegl:matting-global". So it
      won't be a problem even then.
      When the operation is present though, it definitely makes a lot more
      sense than matting global as default, because it performs a lot better
      in most cases (as far as I could see as well as others).
      (cherry picked from commit b52cdf4c)
  7. 28 Jun, 2020 1 commit
    • Ell's avatar
      app: increase idle priority for hiding on-hover tool-group menu · 3212da71
      Ell authored
      In GimpToolButton, when in "show menu on hover" mode, increase the
      idle priority for hiding the the tool-group menu upon button/menu
      leave-notify.  Make the priority one step below the normal event
      priority, so that a subsequent button/menu enter-notify event
      canceling the idle is processed beforehand, while the idle is
      otherwise still processed before ordinary lower-priority sources,
      in particular, before projection rendering timeouts.
  8. 16 Jun, 2020 1 commit
    • Ell's avatar
      Issue #5226 - hover over toolgroup not working · 00145da3
      Ell authored
      In gimp_tool_button_enter_notify(), only mask-in the mouse-button
      state for determining whether to show the tool-group menu.  This
      avoids other bits of state -- in particular, certain keyboard
      locks, including keyboard-layout state -- from preventing the menu
      from showing.
  9. 12 Jun, 2020 1 commit
  10. 11 Jun, 2020 5 commits
  11. 10 Jun, 2020 1 commit
  12. 09 Jun, 2020 1 commit
  13. 07 Jun, 2020 2 commits
  14. 03 Jun, 2020 2 commits
  15. 02 Jun, 2020 9 commits
  16. 01 Jun, 2020 4 commits
  17. 31 May, 2020 1 commit