1. 08 Feb, 2019 2 commits
  2. 07 Feb, 2019 1 commit
    • Jehan's avatar
      po: fix the context (msgctx) for 2 strings. · 7a5e5be3
      Jehan authored
      See commit f8f3a749.
      The context change was basically a bug fix, and nothing changed in the
      original string, nor its actual GUI context/usage. Therefore there is no
      need to invalidate the translations (mark it "fuzzy", which would be
      what would happen automatically after this change) for the 43 languages
      which already translated these. Let's just search-and-replace all the po
      files with the correct context.
      
      For the record, I got the green light from several translators on
      gnome-i18n ML so let's fix. :-)
      7a5e5be3
  3. 06 Feb, 2019 2 commits
  4. 31 Jan, 2019 1 commit
  5. 30 Jan, 2019 2 commits
  6. 28 Jan, 2019 1 commit
  7. 27 Jan, 2019 1 commit
  8. 26 Jan, 2019 3 commits
  9. 23 Jan, 2019 1 commit
  10. 22 Jan, 2019 1 commit
  11. 21 Jan, 2019 1 commit
  12. 18 Jan, 2019 1 commit
  13. 17 Jan, 2019 1 commit
  14. 15 Jan, 2019 1 commit
  15. 14 Jan, 2019 1 commit
  16. 13 Jan, 2019 1 commit
  17. 12 Jan, 2019 1 commit
  18. 10 Jan, 2019 3 commits
  19. 09 Jan, 2019 3 commits
  20. 08 Jan, 2019 1 commit
  21. 06 Jan, 2019 1 commit
  22. 04 Jan, 2019 2 commits
  23. 27 Dec, 2018 1 commit
    • Ell's avatar
      app: remove "Edit -> Fade..." · ed7ea51f
      Ell authored
      This commit completely removes the "Edit -> Fade..." feature,
      because...
      
      - The main reason is that "fade" requires us to keep two buffers,
        instead of one, for each fadeable undo step, doubling (or worse,
        since the extra buffer might have higher precision than the
        drawable) the space consumed by these steps.  This has notable
        impact when editing large images.  This overhead is incurred even
        when not actually using "fade", and since it seems to be very
        rarely used, this is too wasteful.
      
      - "Fade" is broken in 2.10: when comitting a filter, we copy the
        cached parts of the result into the apply buffer.  However, the
        result cache sits after the mode node, while the apply buffer
        should contain the result of the filter *before* the mode node,
        which can lead to wrong results in the general case.
      
      - The same behavior can be trivially achieved "manually", by
        duplicating the layer, editing the duplicate, and changing its
        opacity/mode.
      
      - If we really want this feature, now that most filters are GEGL
        ops, it makes more sense to just add opacity/mode options to the
        filter tool, instead of having this be a separate step.
      ed7ea51f
  24. 24 Dec, 2018 1 commit
  25. 23 Dec, 2018 1 commit
  26. 16 Dec, 2018 1 commit
  27. 12 Dec, 2018 2 commits
  28. 09 Dec, 2018 1 commit
  29. 08 Dec, 2018 1 commit