1. Jan 29, 2014
  2. Jan 27, 2014
  3. Dec 03, 2013
  4. Oct 30, 2013
    • Gunnar Sletta's avatar
      Use one render loop per QQuickWindow · 906d5c5c
      Gunnar Sletta authored
      
      See the task for the full reasoning behind this patch.
      
      The threaded renderloop has been refactored to have one window per
      thread. This is mostly a simplification of the current code path where
      for loops over multiple windows are turned into if (window).
      
      The QSGContext has been split into two classes, QSGRenderContext
      for which there is one per OpenGLContext.
      
      The rest of the patch is name changes and a couple of cleanups
      in the hopes of simplifying this change.
      
      Task-number: QTBUG-33993
      
      Change-Id: I31c81f9694d7da7474a72333169be38de62613c4
      Reviewed-by: default avatarSean Harmer <sean.harmer@kdab.com>
      906d5c5c
  5. Oct 24, 2013
  6. Oct 02, 2013
  7. Sep 30, 2013
  8. Sep 25, 2013
  9. Sep 12, 2013
  10. Jul 03, 2013
  11. Jun 23, 2013
  12. Jun 14, 2013
  13. Jun 11, 2013
  14. Jun 07, 2013
  15. May 22, 2013
  16. Apr 30, 2013
  17. Apr 25, 2013
  18. Apr 24, 2013
  19. Apr 04, 2013
  20. Apr 02, 2013
  21. Mar 20, 2013
    • Pierre Rossi's avatar
      Optimize QQuickTextEdit for larger documents. · f513e884
      Pierre Rossi authored
      
      The rationale is to not end up re-processing the whole document on each update
      Since we know where the editing takes place, we can break down the text edit's
      contents in several text nodes and only re-create the affected text nodes upon
      editing.
      
      This requires ripping out the SelectionEngine helper class from QQuickTextNode
      so that QQuickTextEdit can tap into its functionality directly.
      
      A positive side-effect of this exercise is that it should be much harder to
      to come across GlyphNodes packing more than 16300 glyphs or so.
      
      Task-number: QTBUG-29596
      Change-Id: Id29b0709baa43f5b29c44ab02398ba996be3e28a
      Reviewed-by: default avatarYoann Lopes <yoann.lopes@digia.com>
      f513e884
  22. Mar 19, 2013
    • Frederik Gladhorn's avatar
      Make sure that TextInteractionFlags get set. · 7148a797
      Frederik Gladhorn authored
      
      The first time the function is called,
      it could fail to set the flags.
      
      Calling setSelectByKeyboard(true) would not actually
      set the text interaction flags (was == on).
      
      The test didn't detect it because it called setReadOnly
      before setSelectByKeyboard.
      
      Change-Id: Ia54cc782b6ad5a74f1d7029c92fa230116d034b0
      Reviewed-by: default avatarJ-P Nurmi <jpnurmi@digia.com>
      7148a797
  23. Mar 15, 2013
  24. Mar 13, 2013
  25. Mar 07, 2013
  26. Mar 04, 2013
  27. Mar 01, 2013
  28. Feb 19, 2013
  29. Jan 10, 2013
  30. Nov 26, 2012
  31. Sep 23, 2012
  32. Aug 09, 2012
  33. Aug 08, 2012
    • Bea Lam's avatar
      Fix uses of various qml doc commands · b2120f68
      Bea Lam authored
      
      Signals documented with \qmlsignal should indicate handler name,
      i.e. 'onSignal' rather than 'signal'.
      
      Methods documented with \qmlmethod do not need to document 'void'
      return values.
      
      Also the name of any documented attribute should be qualified
      with 'QtQuick2::<qmltype>'.
      
      Change-Id: I206dd9e8f39c3b84e029ae9d4101b05d0bfb3478
      Reviewed-by: default avatarAndrew den Exter <andrew.den-exter@nokia.com>
      b2120f68
  34. Aug 06, 2012
  35. Aug 03, 2012
  36. Jul 30, 2012
  37. Jul 17, 2012