1. 19 Oct, 2018 1 commit
    • Josef Ridky's avatar
      Issue #2087 - Issues discovered by coverity scan · 2987f012
      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)
      
      (cherry picked from commit 56c8f832)
      2987f012
  2. 29 Sep, 2018 7 commits
  3. 19 Aug, 2018 1 commit
    • Jehan's avatar
      Issue #1970: Python-fu missing in 2.10.4. · de11e353
      Jehan authored
      Do not set the interpreter to `python2` but to whatever was found by the
      AM_PATH_PYTHON2() m4 macro.
      It looks like the Python2 binary we ship in our DMG may be call "python"
      only (without the '2'). Let's just make our code more resilient to
      various builds.
      I am not sure yet this is the only/actual problem for this issue on
      macOS, but this is at least in the right way.
      
      (cherry picked from commit 8f21c948)
      de11e353
  4. 18 Aug, 2018 1 commit
    • Jehan's avatar
      plug-ins: include the right python source in the distribution. · b810590b
      Jehan authored
      The python path with directory are generated files and should not be in
      the dist. The previous commit was fixing an in-tree `make check` but
      this one fixes the `make distcheck` as the dist was packaging the wrong
      python files.
      
      (cherry picked from commit 55a7872e)
      b810590b
  5. 18 Jul, 2018 1 commit
    • Jehan's avatar
      Issue #788: also install all python plug-ins in their own directory. · dbb9555d
      Jehan authored
      It seems I forgot to also install python plug-ins in a subdirectory
      (because they are deactivated on master for the time being). I even
      found a year-old patch from myself rotting in the tracker, and which was
      doing exactly this.
      I redid it, improved to fit changes.
      dbb9555d
  6. 11 Jul, 2018 1 commit
  7. 16 Jun, 2018 3 commits
    • Salamandar's avatar
      Fix Python files: · 15075932
      Salamandar authored
      * Prefer python2 to python that may point on python3 on modern installs.
      * Fix indent/spaces consistency.
      
      (cherry picked from commit 22657012)
      15075932
    • Jehan's avatar
      plug-ins: recognize "python2" env to launch the python interpreter. · 3c6f789c
      Jehan authored
      (cherry picked from commit 769325e5)
      3c6f789c
    • Jehan's avatar
      m4macros, plug-ins: run more accurately the "python2" interpreter. · 42b13216
      Jehan authored
      Our configure test checks the presence of a Python2, but then uses
      "python" as interpreter, which is a problem nowadays as the default
      python is set to be Python 3 on some distributions (and this will be
      more and more the case). So GIMP may end up trying to run our plug-ins
      through Python 3 (which would fail) even if Python 2 is present.
      Now AM_PATH_PYTHON2() m4 macro will set $PYTHON to a more accurate
      Python version as priority.
      
      Similarly let's use "python2" in the binfmt string for extension search.
      
      (cherry picked from commit 03ea9cac)
      42b13216
  8. 15 Jun, 2018 1 commit
    • Jehan's avatar
      Issue #248: Python console doesn't support input()/raw_input(). · 79d55e09
      Jehan authored
      As noted by Massimo, we can just make the argument of raw_input() an
      optional argument.
      
      Also adding a modal implementation for input() so that it doesn't lock
      the Python console waiting from input from the plug-in stdin. As noted
      in Python doc, input() is equivalent to `eval(raw_input(prompt))`.
      Not all that safe, but in the end, it is the developer's responsibility.
      
      (cherry picked from commit 130ef5ce)
      
      Note: it is untested on master since we don't have Python right now, but
      I don't see why it would not work here as well!
      79d55e09
  9. 20 May, 2018 2 commits
  10. 28 Apr, 2018 1 commit
  11. 25 Apr, 2018 1 commit
  12. 23 Apr, 2018 1 commit
  13. 18 Apr, 2018 1 commit
  14. 09 Jan, 2018 2 commits
    • Jehan's avatar
      plug-ins, themes: use the "normal text" color as stdout color of... · 657c39dc
      Jehan authored
      ... the python console.
      It was using "selected text", which is most often inverted color (close
      if not identical to the background color). As a consequence, it made
      stdout output unreadable by default, forcing themes to always define a
      style for the python console. Using "normal text" is a much better
      choice to default to something readable from a parent style.
      
      As a consequence, I also removed "python-fu-console" styling from the
      System theme, where there should be as few theming as possible.
      657c39dc
    • Massimo Valentini's avatar
      Bug 753736: GIMP Python green prompt is virtually... · e663526d
      Massimo Valentini authored
      ... unreadable to those with certain type of color blindness
      e663526d
  15. 06 Jan, 2018 1 commit
  16. 04 Jan, 2018 1 commit
  17. 01 Jan, 2018 1 commit
    • Massimo Valentini's avatar
      Bug 783336: exported openraster (.ora) missing... · cd4a0a18
      Massimo Valentini authored
      ...mergedimage.png
      
      fix also the thumbnail creation, that:
      must be 8 bit; should not be upscaled; should not have frame
      or decoration, that I interpreted as when there are transparent
      areas they should not be blended with a background color,
      so instead of image_flatten use  image_merge_visible_layers
      (also for the merged_image)
      cd4a0a18
  18. 03 Sep, 2017 1 commit
  19. 30 Aug, 2017 1 commit
  20. 21 Aug, 2017 1 commit
    • Michael Natterer's avatar
      Move the new "default_new_layer_mode" APIs to the image... · e16c8a23
      Michael Natterer authored
      ...in both the core and libgimp.
      
      Images now know what the default mode for new layers is:
      
      - NORMAL for empty images
      - NORMAL for images with any non-legacy layer
      - NORMAL_LEGAVY for images with only legacy layers
      
      This changes behavior when layers are created from the UI, but *also*
      when created by plug-ins (yes there is a compat issue here):
      
      - Most (all?) single-layer file importers now create NORMAL layers
      - Screenshot, Webpage etc also create NORMAL layers
      
      Scripts that create images from scratch (logos etc) should not be
      affected because they usually have NORMAL_LEGACY hardcoded.
      
      3rd party plug-ins and scripts will also behave old-style unless they
      get ported to gimp_image_get_default_new_layer_mode().
      e16c8a23
  21. 20 Aug, 2017 1 commit
  22. 31 May, 2017 2 commits
  23. 25 May, 2017 1 commit
    • Jehan's avatar
      plug-ins: install python-console plug-in in its own subdirectory. · e9851102
      Jehan authored
      As a consequence of commit efae55a7, plug-ins should not install
      data/library files alongside on the root plug-ins/ directory. If they
      have such files, they should create a subdirectory named as the entry
      point file. Obviously we should be the first to follow this guideline.
      We had one such plug-in: python-console.py, which is importing
      pyconsole.py. Let's have both these files under
      plug-ins/python-console/.
      e9851102
  24. 18 Apr, 2017 1 commit
  25. 21 Mar, 2017 1 commit
  26. 16 Mar, 2017 1 commit
  27. 26 Feb, 2017 1 commit
  28. 09 Jan, 2017 2 commits