1. Mar 06, 2012
  2. Mar 05, 2012
  3. Mar 02, 2012
    • Laszlo Agocs's avatar
      Use velocity from touch events only when they are valid · 82a252af
      Laszlo Agocs authored
      
      Add the capability flags to the extended mouse events. Otherwise it is
      not possible to tell if the velocity is valid.
      
      While the original version is fine if velocity is guaranteed to be
      available whenever QT_TRANSLATE_TOUCH_TO_MOUSE is set, some platform
      and driver combinations, e.g.  the evdevtouch plugin that comes with
      Qt, do not provide velocity data in touch events. The touch-only mode
      of QML may be very useful in these cases too, we just need to fall
      back to the built-in velocity calculation.
      
      Change-Id: Iec5e7632a66380dc04c9435b09f5c173107bbe00
      Reviewed-by: default avatarMartin Jones <martin.jones@nokia.com>
      82a252af
  4. Mar 01, 2012
  5. Feb 28, 2012
  6. Feb 27, 2012
  7. Feb 24, 2012
  8. Feb 21, 2012
  9. Feb 20, 2012
  10. Feb 15, 2012
  11. Feb 13, 2012
  12. Feb 10, 2012
  13. Feb 08, 2012
  14. Feb 07, 2012
  15. Feb 06, 2012
  16. Feb 02, 2012
  17. Feb 01, 2012
  18. Jan 30, 2012
  19. Jan 25, 2012
  20. Jan 24, 2012
  21. Jan 23, 2012
  22. Jan 17, 2012
  23. Jan 13, 2012
  24. Jan 02, 2012
    • Kim Motoyoshi Kalland's avatar
      Don't re-parent ShaderEffect source items. · 6aa535e3
      Kim Motoyoshi Kalland authored
      
      ShaderEffect and ShaderEffectSource used to set themselves as
      parent of and hide source items that don't already have a parent.
      This was done in order to make sure the source items got a canvas.
      This patch sets the canvas of the source items without re-parenting.
      
      Task-number: QTBUG-23069
      Change-Id: I24d56e6eb970590bca3adff7a61459d25e4983a0
      Reviewed-by: default avatarGunnar Sletta <gunnar.sletta@nokia.com>
      6aa535e3
    • Frederik Gladhorn's avatar
      Add accessibility to qml · 27a497b3
      Frederik Gladhorn authored
      
      This consists of two parts:
      An attached property for QML items and a plugin for the accessibility framework.
      
      The attached property simply takes care of some properties (name, role)
      that are needed in order to expose semantics of the application to
      assistive tools.
      
      The plugin exposes the hierarchy of QML items to the
      accessibility framework.
      
      Change-Id: I32f5603d0d9549b01b3645b205b710b9801762f7
      Reviewed-by: default avatarJan-Arve Sæther <jan-arve.saether@nokia.com>
      27a497b3
  25. Dec 28, 2011
  26. Dec 20, 2011
  27. Dec 19, 2011
  28. Dec 14, 2011
  29. Dec 12, 2011
  30. Dec 09, 2011
  31. Dec 08, 2011
    • Gunnar Sletta's avatar
      Implemented multiple windows and GL context sharing · fdd14a1a
      Gunnar Sletta authored
      
      What was traditionally the QQuickRenderLoop which was used
      to support one QQuickCanvas instance has now grown to support
      multiple QQuickCanvas instances and is now called
      QQuickWindowManager, of which there are two implementations.
      
      QQuickRenderThreadSingleContextWindowManager:
      One QSGContext and one OpenGL context is being used to draw
      all the windows and we alternate between which surface the gl
      context is bound to. This implementation relies on that
      swap does not block, but that the graphics pipeline is
      vsynced and will eventually block as the buffer queue is
      filled up. This is the behavior we get on Mac OS X and
      Wayland. The benefit of this implementation is that we have
      vsync'ed animations, and the synchronizaiton between GUI and
      render thread is simple. (well, simple relative to the
      alternative, that is).
      
      QQuickTrivialWindowManager:
      One QSGContext and one OpenGL context is being used on the GUI
      thread. Animations are ticked from a timer. Performance of this
      implementation will deteriorate if the driver is using blocking
      swap.
      
      Task-number: QTBUG-19455
      Change-Id: Ib961ac7d71eb49c70a057872b7cac020c4d19f3d
      Reviewed-by: default avatarSamuel Rødal <samuel.rodal@nokia.com>
      fdd14a1a
  32. Dec 02, 2011
    • Kent Hansen's avatar
      Say hello to QtQuick module · 6c8378ea
      Kent Hansen authored
      
      This change moves the QtQuick 2 types and C++ API (including
      SceneGraph) to a new module (AKA library), QtQuick.
      
      99% of this change is moving files from src/declarative to
      src/quick, and from tests/auto/declarative to
      tests/auto/qtquick2.
      
      The loading of QtQuick 2 ("import QtQuick 2.0") is now delegated to
      a plugin, src/imports/qtquick2, just like it's done for QtQuick 1.
      
      All tools, examples, and tests that use QtQuick C++ API have gotten
      "QT += quick" or "QT += quick-private" added to their .pro file.
      
      A few additional internal QtDeclarative classes had to be exported
      (via Q_DECLARATIVE_PRIVATE_EXPORT) since they're needed by the
      QtQuick 2 implementation.
      
      The old header locations (e.g. QtDeclarative/qquickitem.h) will
      still be supported for some time, but will produce compile-time
      warnings. (To avoid the QtQuick implementation using the
      compatibility headers (since QtDeclarative's includepath comes
      first), a few include statements were modified, e.g. from
      "#include <qsgnode.h>" to "#include <QtQuick/qsgnode.h>".)
      
      There's a change in qtbase that automatically adds QtQuick to the
      module list if QtDeclarative is used. Together with the compatibility
      headers, this should help reduce the migration pain for existing
      projects.
      
      In theory, simply getting an existing QtDeclarative-based project
      to compile and link shouldn't require any changes for now -- but
      porting to the new scheme is of course recommended, and will
      eventually become mandatory.
      
      Task-number: QTBUG-22889
      Reviewed-by: default avatarLars Knoll <lars.knoll@nokia.com>
      Change-Id: Ia52be9373172ba2f37e7623231ecb060316c96a7
      Reviewed-by: default avatarKent Hansen <kent.hansen@nokia.com>
      Reviewed-by: default avatarSergio Ahumada <sergio.ahumada@nokia.com>
      6c8378ea