1. 20 May, 2018 13 commits
  2. 12 May, 2018 2 commits
  3. 07 May, 2018 2 commits
  4. 26 Apr, 2018 1 commit
  5. 24 Apr, 2018 1 commit
  6. 23 Apr, 2018 4 commits
  7. 21 Apr, 2018 1 commit
  8. 17 Apr, 2018 1 commit
  9. 16 Apr, 2018 3 commits
  10. 15 Apr, 2018 3 commits
    • Michael Natterer's avatar
      pdb: deprecate all non-clipboard functions in the "edit" group · 5ee67dee
      Michael Natterer authored
      Still have to port script-fu scripts...
      5ee67dee
    • Michael Natterer's avatar
      pdb: improve docs of deprecated functions · ef3edece
      Michael Natterer authored
      Don't unconditionally overwrite all the proc's description, author
      etc.  Instead, try to preserve them and append the "Deprecated" notes
      to the help texts and generated comments.
      
      Only affects one procedure because we killed the meta info of all
      other deprecated procs so far, but now we don't have to do that any
      longer.
      ef3edece
    • Michael Natterer's avatar
      Bug 795230 - Rename Blend tool and provide PDB compatibility · 50536e1c
      Michael Natterer authored
      Add new PDB group "drawable_edit" which has all procedures from the
      "edit" group which are not cut/copy/paste.
      
      The new group's procedures don't have opacity, paint_mode
      etc. arguments but take them from the context instead. Unlike the old
      gimp-edit-fill, gimp-drawable-edit-fill now uses the context's opacity
      and paint_mode.
      
      The new gimp-drawable-edit-gradient-fill procedure uses even more
      context properties which are also newly added with this commit
      (gradient_color_space, gradient_repeat_mode, gradient_reverse).
      
      And some cleanup in context.pdb.
      
      This is still WIP, nothing in the edit group is depcreated yet.
      50536e1c
  11. 13 Apr, 2018 1 commit
  12. 10 Apr, 2018 1 commit
  13. 08 Apr, 2018 2 commits
  14. 07 Apr, 2018 1 commit
  15. 04 Apr, 2018 4 commits
    • Jehan's avatar
      libgimp: add an exception handler for Windows. · fa02a2c6
      Jehan authored
      Drmingw already added its own exception handler which generates crash
      traces in a text file, for plug-ins as well. This additional handler is
      run after Drmingw handler and allows us to do things on our own, and in
      particular we could display the content of the debug traces.
      
      Right now it simply prints these to stderr, which actually won't be of
      much use on Win32, first because the console is deactivated on stable
      releases, also because after tests, it doesn't look like even running
      GIMP from cmd outputs to console either.
      
      We currently don't use the same debug dialog as the core on purpose,
      because we don't want everyone to send us traces for every unmaintained
      third party plug-ins out there. But we should definitely allow easier
      trace possibilities at some point, first to improve/debug our own core
      plug-ins, and also to help third party plug-in developers!
      So this commit is not making visible changes yet but is actually a first
      step towards these debugging goals.
      fa02a2c6
    • Jehan's avatar
      libgimp: various warning fixes for Win32. · 76bce77d
      Jehan authored
      76bce77d
    • Jehan's avatar
      libgimp: do not end the fatal and signal handlers with gimp_quit(). · 9c8a8ae5
      Jehan authored
      When ending with gimp_quit(), GIMP was not displaying the "Plug-in
      crashed" error dialog, which is not good, since we lose the crash
      feedback for plug-ins. Just let the plug-in continue its normal run in
      order to get the error dialog.
      Also protect the tracing functions, which are not working on Win32.
      9c8a8ae5
    • Jehan's avatar
      libgimp: add a gimp_fatal_func() allowing stack tracing plug-ins on... · e98b9376
      Jehan authored
      ... various crashes.
      e98b9376