Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. QQuickWidget vs QQuickView

QQuickWidget vs QQuickView

Scheduled Pinned Locked Moved QML and Qt Quick
3 Posts 2 Posters 5.2k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F Offline
    F Offline
    Frime
    wrote on last edited by
    #1

    Hi together,

    I'm currently working on a plugin for a plugin-based open source project. I decided to implement the UI part with QML, rendered by an QQuickWidget into the QWidget-based UI.
    But i have a lot of problems with this

    • External Drag and Drop doesn't work properly
    • Rendering performance is really bad (juddery animations and so on)

    if I open my QML Code in a external QQuickView (instead of a embedded QQuickWidget) all works really good and fluid... Does anybody has an idea why these two components behaves completely different?

    My setup: Qt 5.4 OS-X 10.9.5

    Thank you very much in advance!
    Frime

    1 Reply Last reply
    0
    • JKSHJ Offline
      JKSHJ Offline
      JKSH
      Moderators
      wrote on last edited by JKSH
      #2

      Hi @Frime,

      Widgets are a much older technology. Mixing Qt Quick with Qt Widgets requires some compromises, which reduces performance. See the QQuickWidget documentation:

      QQuickWidget.... comes at the expense of performance. Unlike QQuickWindow and QQuickView, QQuickWidget involves rendering into OpenGL framebuffer objects. This will naturally carry a minor performance hit.
      ...
      Using QQuickWidget disables the threaded render loop on all platforms. This means that some of the benefits of threaded rendering, for example Animator classes and vsync driven animations, will not be available.

      QQuickView is not restricted by old widget technology, so it performs better.

      Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches

      F 1 Reply Last reply
      1
      • JKSHJ JKSH

        Hi @Frime,

        Widgets are a much older technology. Mixing Qt Quick with Qt Widgets requires some compromises, which reduces performance. See the QQuickWidget documentation:

        QQuickWidget.... comes at the expense of performance. Unlike QQuickWindow and QQuickView, QQuickWidget involves rendering into OpenGL framebuffer objects. This will naturally carry a minor performance hit.
        ...
        Using QQuickWidget disables the threaded render loop on all platforms. This means that some of the benefits of threaded rendering, for example Animator classes and vsync driven animations, will not be available.

        QQuickView is not restricted by old widget technology, so it performs better.

        F Offline
        F Offline
        Frime
        wrote on last edited by
        #3

        @JKSH Thank you very much! I overlooked that.

        Now, I embed the QQuickView within a Window-Wrapper [createWindowContainer(..)]. Performance is much better, but resizing results in evil black/white flickering - especially on linux. But this is something I can deal with. Thanks!

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved