1. 26 Mar, 2016 2 commits
  2. 25 Mar, 2016 10 commits
    • Stefano Bonicatti's avatar
      Remove the need to rename boost dll and lib · c0147862
      Stefano Bonicatti authored
      Instead of specifying msvc as toolset, we specify msvc-14.0 which always
      names the lib and dll correctly.
      Added the copy of the boost dll to the bin directory since it's sometimes
      required when running Krita from QtCreator or manually.
    • Halla Rempt's avatar
      BUG:350115 Save all used brush tips in the bundle · f1c69c15
      Halla Rempt authored
      If a preset needs a brush tip file, this is now automatically added
      on saving the bundle.
    • Halla Rempt's avatar
      BUG: 360909 Remove spurious assert · 526e1f92
      Halla Rempt authored
      This assert kicks off when undoing a quick clipping group to no
      good purpose: it doesn't prevent a real crash or any other bug,
      it just startles the user into reporting a bug.
    • Halla Rempt's avatar
      Fix build on OSX · c6e99358
      Halla Rempt authored
    • László Fazekas's avatar
      D1215 Wacom tablet crash in Krita · 5da2ff72
      László Fazekas authored
    • Halla Rempt's avatar
      Update to G'Mic 1.7 · 505966cb
      Halla Rempt authored
    • Stefano Bonicatti's avatar
      Correct KoColorSpaceRegistry patch · bcd977e8
      Stefano Bonicatti authored
      Limit the readlock to a smaller scope and user QReadLocker.
      Wrote a more insightful comment about why it is necessary to recheck
      the colorspace presence in the cache.
      Code style fix.
    • Dmitry Kazakov's avatar
      Fix "openGL lag at zoom 2000 + rotation" · 08fd3aa8
      Dmitry Kazakov authored
      The problem was not related to the openGL actualy. It was caused
      by the implementation of QPainter::clipRegion() which generated
      20k+ rectangles from a rotated rect when rotation angle was near to
      a 0 or 90deg.
      WARNING for the future:
      Never use QPainter::clipRegion(). Use KisPaintingUtils::safeClipRegion()
      instead. It workarounds the issue returning a bit bigger rect.
      Fixes T1446
    • Dmitry Kazakov's avatar
      Fix a hangup when closing Krita when running LoD strokes · 13df6317
      Dmitry Kazakov authored
      1) The strokes should have a strong pointer to the image, because
         theoretically they can work with it even when the document is
         already closed. It also means that the destructor of the image
         cannot be entered before all the background strokes have finished
      2) Added waitForDone() call *before* entering the KisImage destructor.
         The problem is that while running a destructor, all the weak pointers
         temporary enter an inconsistent state. So we should wait for the strokes
         to finish before that. See a comment in the destructor of KisDocument.
      Fixes T1858
    • László Fazekas's avatar
      D1199 patch for a crash during document close · 8fef07fc
      László Fazekas authored
      The animation interface is using the rootlayer of the image. This patch creates the interface
      after the rootlayer and deletes it before the rootlayer deleted.
  3. 24 Mar, 2016 15 commits
  4. 23 Mar, 2016 7 commits
    • Stefano Bonicatti's avatar
      Avoid double unlock · cb94ccc6
      Stefano Bonicatti authored
    • Stefano Bonicatti's avatar
      Add missing lock · e578a55e
      Stefano Bonicatti authored
    • Stefano Bonicatti's avatar
      Fix colorspace registry leaking · fc341de9
      Stefano Bonicatti authored
      Multiple threads could find that the colorspace wasn't cached and decide
      that they had to create it, so when taking the write lock we check if
      the colorspace isn't actually already in the cache.
      This check fixes also a second issue where, not having the colorspace
      factory cache, and since the profileName might be different after having
      checked the cache, we might create a colorspace that was already in the cache.
      A practical example is the colorspace profile "XYZ identity built-in", which
      we say it's in the cache, then a colorspace using "XYZ identity built-in (Default)"
      is searched with the colorSpace function. That profile name happens to be an alias
      of the one in the cache, but we first search for the aliased name and not finding it,
      without this patch, we could decide that we have to create a new colorspace and
      overwrite the other one in the cache, doing this everytime that colorspace is
      The patch also optimize the access to the caches using an iterator so that
      we know if a colorspace is present and eventually take its pointer without
      multiple accesses to the cache.
    • László Fazekas's avatar
    • László Fazekas's avatar
    • László Fazekas's avatar
    • Halla Rempt's avatar
      Use the highlight color for the selected tool · 441a6fa5
      Halla Rempt authored
      This also 'fixes' the setting of the highlight color in
      the toolbar, we should be taking the app's palette, not the
      one set on the current widget.
  5. 22 Mar, 2016 6 commits