1. 16 Jun, 2017 1 commit
    • Dmitry Kazakov's avatar
      Implement KoShape::updateAbsolute() for complex transformation updates · 6f51599f
      Dmitry Kazakov authored
      Historically, transformation code uses extremely weird method of shape
      updates that rely on the event loop. This patch implements a framework
      for moving away from this strategy.
      
      The problem:
      
      When one transforms a shape he needs to update both areas: bounding
      rect of the shape *before* the transform and a bounding rect of the shape
      *after* the transform. Before the patch, the transformation code used the
      system like that:
      
      shape->update();
      shape->setTransformation(newTransform);
      shape->update();
      
      That works only with assumption that the first update() call will *not*
      be executed before setTransform() call. That should be true atm, but it
      is not guaranteed to be so in the future. Therefore, now the update happens
      like that:
      
      const QRectF oldDirtyRect = shape->boundingRect();
      shape->setTransformation(newTransform);
      shape->updateAbsolute(oldDirtyRect | shape->boundingRect());
      6f51599f
  2. 17 Feb, 2017 1 commit
  3. 06 Feb, 2017 2 commits
  4. 30 Dec, 2016 1 commit
  5. 29 Dec, 2016 1 commit
  6. 23 Dec, 2016 3 commits
  7. 07 Jul, 2016 1 commit
  8. 26 Jan, 2016 1 commit
  9. 09 Jan, 2016 1 commit
  10. 26 Nov, 2015 2 commits
  11. 10 Sep, 2015 1 commit
  12. 07 Jan, 2015 1 commit
  13. 27 Sep, 2014 1 commit
  14. 06 Apr, 2013 1 commit
    • Boudewijn Rempt's avatar
      Make all KDE includes consistent · 83da42dc
      Boudewijn Rempt authored
      We used CamelCase and .h includes all mixed up. This patch chances all
      includes to .h style.
      
      I choose that style over CamelCase for the following reasons
      
      * the change was easier to automate
      * CamelCase include files are created manually and so have inconsistencies
      * the majority of Calligra KDE includes were .h style
      83da42dc
  15. 29 Jan, 2013 1 commit
    • C. Boemann's avatar
      Change KoTextAnchor into three new classes · ffd625c6
      C. Boemann authored
       KoShapeAnchor - which in theory should be moved to flake later
       KoAnchorInlineObject - which is the kotext part responsible for being an inline (asChar) object
       KoAnchorTextRange - which is the kotext part resposible for toChar and toParagraph anchoring
      
      Now the user no longer have to contend with invisible characters acting as anchors. These kinds
      of anchors are now placed at a cursor position instead (using KoTextRange)
      
      This also has the benefit that we can support toParagraph anchoring a bit better, as it's no
      longer possible to move the anchor character away from the paragraphs first position.
      
      REVIEW: 108459
      ffd625c6
  16. 13 Jan, 2013 1 commit
    • C. Boemann's avatar
      Shape moving restrictions based on anchor properties. · 8bd52912
      C. Boemann authored
      This is the page anchors equivalent of the char and paragraph anchors code we
      already have.
      
      This makes a difference both on initial layout (nice improvements)
      and on interactive moving of page anchored shapes.
      
      This commit also fixes the default anchoring properties to be the same as in LO.
      
      This commit also fixes it so the page anchored iages doesn't leave empty rects on
      page 1 after reload
      
      BUG: 312193
      BUG: 310715
      BUG: 312982
      REVIEW: 108358
      8bd52912
  17. 04 Jul, 2012 1 commit
  18. 29 Apr, 2012 1 commit
    • Thorsten Zachmann's avatar
      Fix painting artefacts after snapping has be used. · 57c03c6c
      Thorsten Zachmann authored
      Update the position the snap is shown before and after moving.
      Reset the data once the action is finished.
      Update the canvas when the interaction is finished so the snap guid is no longer visible.
      
      OK to backport?
      
      BUG: 260418
      57c03c6c
  19. 08 Oct, 2011 1 commit
    • Boudewijn Rempt's avatar
      Separate KoResourceManager for canvas and document · 0b2d5353
      Boudewijn Rempt authored
      KoResourceManager was used in two places: the canvas and document
      classes. This gave rise to endless confusion about which resource
      manager should be used where and contains what. The KoResourceManager
      api also contained methods that were only relevant when used from
      a document and others that were only relevant when used from a canvas.
      
      This patch splits the resourcemanager into two public and one private
      class. The public classes are KoDocumentResourceManager and
      KoCanvasResourceManager, the private class is KoResourceManager. The
      public classes defer to the private class for code-sharing purposes.
      
      The old KoCanvasResource and KoDocumentResource enums have been taken
      into the classes themselves.
      0b2d5353
  20. 21 Jun, 2011 1 commit
  21. 22 Mar, 2011 1 commit
    • Jan Hambrecht's avatar
      make handle radius and grab sensitivity application wide settings · 72d501bf
      Jan Hambrecht authored
      changes the scope of handle radius and grab sensitivity from per canvas
      to per application, i.e. the are shared via the shape controllers
      resource manager. added some convenience methods to KoToolBase and
      KoInteractionStrategy to have fewer places where these settings are
      pulle from the proper resource manager.
      both settings are now correctly read and saved to the applications
      config file.
      72d501bf
  22. 31 Jul, 2010 2 commits
  23. 23 Apr, 2010 1 commit
  24. 29 Jan, 2010 1 commit
  25. 23 Jan, 2010 2 commits
  26. 28 Dec, 2009 1 commit
  27. 04 Nov, 2008 1 commit
  28. 20 Aug, 2008 1 commit
  29. 19 Apr, 2008 1 commit
  30. 11 Feb, 2008 1 commit
  31. 01 Dec, 2007 1 commit
  32. 25 Nov, 2007 2 commits
  33. 15 Oct, 2007 1 commit