1. 29 Mar, 2012 1 commit
  2. 10 Mar, 2012 1 commit
    • Dmitry Kazakov's avatar
      Fixed a crash in the text brush · 7e6d8885
      Dmitry Kazakov authored
      Now the brushes are running in a separate thread, so no QPixmap's
      are available for work.
      Also removes excessive includes of <QPixmap> everywhere
      Please review for backporting to 2.4
  3. 03 Mar, 2012 1 commit
  4. 29 Feb, 2012 1 commit
  5. 17 Feb, 2012 1 commit
  6. 07 Feb, 2012 2 commits
    • Boudewijn Rempt's avatar
      Clean up #includes: use the same style for Qt everywhere · 7748f748
      Boudewijn Rempt authored
       #include <QDialog> instead of #include <qdialog.h>
    • Boudewijn Rempt's avatar
      Change <QtGui/QDialog> style includes to <QDialog> · 02025cd8
      Boudewijn Rempt authored
      This is already a tiny part of preparation for Qt5, where QtGui is split
      into QtGui and QtWidgets. If we use explicit module names in our includes,
      we are liable to churn like this.
      Since KDE applications always have all Qt modules in the include path
      anyway, direct includes always work (both in Qt4 and Qt5), and since we
      already used direct includes in thousands of places, this change makes
      our code more consistent, too.
  7. 06 Feb, 2012 1 commit
  8. 31 Jan, 2012 1 commit
    • Dmitry Kazakov's avatar
      Moved managing dummies out of KisShapeController · 9e1baa22
      Dmitry Kazakov authored
      Now we have a separate class that manages dummies/shapes. It is
      named KisDummiesFacadeBase. KisShapeController is derived from
      this class. That allowed us to break dependency of KisNodeModel from
      KisShapeController. Now it depends on KisDummiesFacadeBase, so we can
      easily create one more KisNodeModel in the Bumpmap filter.
  9. 29 Jan, 2012 1 commit
    • Dmitry Kazakov's avatar
      A huge refactoring for KisNodeModel · e2a4f194
      Dmitry Kazakov authored
      Now the model doesn't depend on the hierarchy of the image. It uses
      the hierarchy of the dummies stored in KiShapeController instead.
      Some bullet points:
      1) KisShapeController connects to the image and forwards the node
      addition/removal signals for other recievers
      2) KisNodeModel is connected to the KisShapeController and listens
      to the forwarded signals. It follows that it doesn't depend on the image
      directly, so there are no problems with multithreading.
      2.5) KisNodeModel does not depend on sigLayersChanged() anymore.
      3) KisShapeController manages when a node should be activated. It emits
      the signal sigActivateNode(KisNodeSP) which is processed by the
      KisNodeManager. It solved many problems at once. First, we needn't
      workaround moving of nodes (KisNodeManager::Private::activeBeforeMove).
      Second we are able to deprecate KisNodeManager::activateNode() now. (It'll be
      done in one of next commmits).
      4) Fixed KisNodeFacade::lowerNode(). Now newly activated node depends on the node
      which is added in the end of the operation, so we should move exactly the node
      which was requested.
      5) A small refactoring for KisLayerBox is done. It was discussed with Boud on irc.
      Not yet fixed issues:
      1) I had to disable Bumpmap filter temporarily, because it didn't
      compile with changed KisNodeModel. It'll be fixed in the following commits.
      2) When loading an image with many layers KisLayerBox does not scroll to
      the active layer.
  10. 25 Jan, 2012 1 commit
  11. 24 Jan, 2012 6 commits
  12. 20 Jan, 2012 1 commit
  13. 18 Jan, 2012 3 commits
  14. 03 Jan, 2012 2 commits
  15. 28 Dec, 2011 1 commit
  16. 24 Dec, 2011 1 commit
  17. 17 Dec, 2011 1 commit
  18. 08 Dec, 2011 1 commit
  19. 05 Dec, 2011 1 commit
  20. 28 Nov, 2011 3 commits
  21. 26 Nov, 2011 1 commit
    • Boudewijn Rempt's avatar
      Fix hang in scratchpad · ba8ef2a3
      Boudewijn Rempt authored
      Use QObject to do the memory management of the KisDefaultBounds object,
      this time. We cannot use pass-by-value because we have a subclass for
      KisDefaultBounds after all.
  22. 21 Nov, 2011 3 commits
    • Boudewijn Rempt's avatar
      Refactor KisDefaultBounds again · 1b6d9635
      Boudewijn Rempt authored
      This time, pass all by value, to avoid the memory management issues that
      crop up when sometimes paint devices share defaultbounds, sometimes
      create them, sometimes get them passed and should delete them.
      For a simple class like this, passing by value is not a huge burden, so
      shouldn't be a problem.
    • Boudewijn Rempt's avatar
      Make compile on WIndows · 60817860
      Boudewijn Rempt authored
      More casting to make sqrt and friends workd
    • Boudewijn Rempt's avatar
      Make compile on Windows · e8e7c88c
      Boudewijn Rempt authored
      There was some really big mess with KisDefaultBounds. I have had to
      reorder the includes and make KisDefaultBounds owned by the paintdevice.
      Also, I split the file in two, one for KisDefaultBounds one for
  23. 31 Oct, 2011 1 commit
    • Boudewijn Rempt's avatar
      Fix color management of the display · a8c01ff9
      Boudewijn Rempt authored
      We took the display profile from the kritarc config file, which when it's
      set by colord or anything else wrong. So make sure that it's easy to get
      the correct colorprofile and use that everywhere.
  24. 30 Oct, 2011 1 commit
  25. 16 Oct, 2011 3 commits