1. 04 Feb, 2019 4 commits
  2. 03 Feb, 2019 2 commits
  3. 02 Feb, 2019 3 commits
  4. 01 Feb, 2019 4 commits
  5. 31 Jan, 2019 6 commits
    • Ryuta Fujii's avatar
      Update Japanese translation · 2ea2e84f
      Ryuta Fujii authored
      2ea2e84f
    • Ell's avatar
      app: fix CRITICAL when initializing the perspective-clone tool · 07d2d5af
      Ell authored
      When initializaing the perspective-clone tool in paint mode, the
      GimpDrawTool may already be active, causing the call to
      gimp_draw_tool_start() to fail with a CRITICAL.  Stop the draw tool
      first, if active, to avoid that.
      07d2d5af
    • Ell's avatar
      app: in perspective-clone tool, fix cursor presicion; hide brush while adjusting · e5c9314a
      Ell authored
      In GimpPerspectiveCloneTool, use PIXEL_CENTER cursor precision
      while setting the source, and place the source-position handle at
      the center of the selected pixel, rather than at its top-left
      corner.
      
      Additionally, disable the paint tool while adjusting the
      perspective, so that the brush outline isn't shown, and the cursor
      precision remains SUBPIXEL, even if the hard-edge option is
      toggled.
      e5c9314a
    • Ell's avatar
      app: add gimp_paint_tool_set_active() · 05dd5029
      Ell authored
      ... which can use to enable/disable certain aspects of
      GimpPaintTool (in particular, brush-outline drawing).  Should be
      used by subclasses, to temporarily disable the paint tool while in
      a non-paint mode (currently, this is only needed by the
      perspective-clone tool; see next commit.)
      05dd5029
    • Ell's avatar
      app: fix cursor precision of source tools · ef281823
      Ell authored
      In GimpCloneTool, set the cursor precision to PIXEL_CENTER while
      setting a source, and have GimpBrushTool snap the brush outline to
      pixel centers.
      ef281823
    • Ell's avatar
      app: fix cursor precision of various tools · 158705e4
      Ell authored
      Fix the cursor precision of the cage-transform, foreground-select,
      n-point deformation, and warp-transform tools.
      158705e4
  6. 30 Jan, 2019 5 commits
  7. 28 Jan, 2019 4 commits
  8. 27 Jan, 2019 2 commits
  9. 26 Jan, 2019 5 commits
  10. 25 Jan, 2019 5 commits
    • Salamandar's avatar
      Undo some (unnecessary) changes. · fc657184
      Salamandar authored
      fc657184
    • Salamandar's avatar
      (source modifs) Fix: Rename macros as it conflicts with Mingw headers. · fc8303dd
      Salamandar authored
      * DATADIR -> GIMPDATADIR
      * SYSCONFDIR -> GIMPSYSCONFDIR
      * DATADIR -> SYSDATADIR (tools/)
      fc8303dd
    • Jehan's avatar
      app: new gimp_spin_scale_set_constrain_drag() and use it on paint... · bff3903f
      Jehan authored
      ... tools' brush options.
      After discussions, it turned out that many people disliked that the spin
      scale for brush size (and some other options) get you fractional values.
      How often do you actually need to get a 4.32 pixel-size brush? And even
      how meaningful is it? On the other hand, you usually want a 4 or a 5
      pixel size brush and it's nearly impossible to get (exactly) by dragging
      the scale widget.
      It is so annoying that some even resort to edit the value with keyboard!
      So I am adding an optional "constrain" feature to GimpSpinScale. It will
      still be possible to get fractional values when constraining is on, for
      instance with keyboard edit (the arrow incrementation also will keep any
      fractional part). So the interaction for such scales is simply reversed
      so that you get integers easily, and fractional parts with a bit more
      effort.
      
      It is not turned on by default (some feature actually need precision and
      we don't want to break the sliders for these) and for the time being, I
      only applied it to all the brush settings in paint tools. Now that it
      exist, we may want to apply this to more scales in various parts of
      GIMP.
      bff3903f
    • Jehan's avatar
      libgimpbase: display thread id of the calling thread as hexadecimal... · 8e013536
      Jehan authored
      ... on macOS.
      The debugger running on macOS is usually lldb and (from the reports we
      get) it looks like lldb displays the tid as hexadecimal on macOS
      (whereas lldb displays decimal tid on Linux! I know, it's confusing, yet
      consistent with crash report experience!). So let's just do the same,
      making it easy to quickly copy-search in order to look up the crashing
      thread (without having to convert from decimal to hexa).
      This is a bit of an approximation as I imagine we could have gdb on
      macOS or whatever edge case. Let's say it's good for the common case and
      still not an error otherwise (just a base conversion away).
      8e013536
    • Ell's avatar
      plug-ins: avoid running pygimp plug-ins derived from gimpplugin.plugin at each startup · 9851bc89
      Ell authored
      When initializing a pygimp plug-in derived from gimpplugin.plugin,
      only pass the plug-in's init() and quit() functions to gimp.main()
      if the plug-in actually implements them, instead of passing the
      default NOP versions.  This avoids plug-ins that don't implement
      init() from being registered as having an init function, causing
      them to be run at each startup.
      9851bc89