1. 18 Apr, 2018 2 commits
  2. 17 Apr, 2018 1 commit
  3. 16 Apr, 2018 3 commits
  4. 15 Apr, 2018 5 commits
  5. 14 Apr, 2018 1 commit
  6. 13 Apr, 2018 3 commits
  7. 10 Apr, 2018 1 commit
    • Michael Natterer's avatar
      Bug 791519 - Unexpected selection from channel · 3f95dc52
      Michael Natterer authored
      Make sure a channel -> selection -> channel roundtrip never does any
      gamma conversion.
      
      In gimp_channel_duplicate(), make sure a created channel has the
      right format, and the right data. Fixes selection -> channel.
      
      When switching off quick mask, call gimp_item_to_selection() instead
      if gimp_selection_load(), the latter was implementing a shortcut which
      is now wrong.
      
      Remove gimp_selection_load() which is now unused.
      
      Unrelated: also remove gimp_selection_save(), it was an obvious
      3-liner used only twice.
      3f95dc52
  8. 09 Apr, 2018 1 commit
  9. 18 Mar, 2018 3 commits
  10. 17 Mar, 2018 3 commits
  11. 15 Mar, 2018 1 commit
  12. 14 Mar, 2018 3 commits
  13. 12 Feb, 2018 1 commit
    • Jehan's avatar
      app: keep track of number of errors and traces in GimpCriticalDialog. · 34fe992f
      Jehan authored
      We don't want an infinite number of traces because it takes some time to
      get. Until now I was keeping track of traces in app/errors.c, but that
      was very sucky because then I was limiting traces per session. Instead
      save them as a variable of a GimpCriticalDialog instance. Therefore only
      generate the traces for WARNING/CRITICAL at the last second, when
      calling the dialog.
      When too many traces are displayed, just fallback to just add error
      messages only. But then even errors without traces can be time-consuming
      (if you have dozens of thousands of errors in a few seconds, as I had
      the other day, updating the dialog for all of them would just freeze the
      whole application for a long time).
      So also keep track of errors as well and as last fallback, just send the
      remaining errors to the stderr.
      34fe992f
  14. 11 Feb, 2018 1 commit
  15. 05 Feb, 2018 2 commits
  16. 28 Jan, 2018 1 commit
  17. 11 Jan, 2018 1 commit
  18. 02 Jan, 2018 1 commit
    • Michael Natterer's avatar
      Bug 762443 - Levels tool Output Level sliders works incorrectly · dce93c7d
      Michael Natterer authored
      Add "clamp-input" (which clamps the input values to [0..1])
      and "clamp-output" (which clips the final result to [0..1]),
      properties, parameters and GUI to:
      
      - GimpLevelsConfig
      - GimpOperationLevels
      - The levels tool dialog
      - The gimp_drawable_levels() PDB API
      
      The old deprecated gimp_levels() PDB API now sets both clamping
      options to TRUE which restores the 2.8 behavior.
      
      Also reorder some stuff in GimpLevelsConfig and elsewhere so the
      levels parameters are always in the same order.
      dce93c7d
  19. 17 Dec, 2017 6 commits