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. How to repaint QWidget encapsulated in QDeclarativeItem in QML?
Qt 6.11 is out! See what's new in the release blog

How to repaint QWidget encapsulated in QDeclarativeItem in QML?

Scheduled Pinned Locked Moved Solved QML and Qt Quick
qtquick 1.0qmlqt 4.8
25 Posts 2 Posters 21.9k Views 1 Watching
  • 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.
  • ? A Former User

    @p3c0 The problem is that I am new to QtQuick and I probably misunderstand something essential. This is how I think things work:

    1. The customPlot->replot(); updates the underlying QWidget
    2. The QGraphicsProxyWidget does the painting of the QDeclarativeItem everytime update is called. But if I call the paint method instead of update I get a compile error, because QDeclarativeItem::paint() is virtual
    p3c0P Offline
    p3c0P Offline
    p3c0
    Moderators
    wrote on last edited by
    #6

    @Chillax

    But if I call the paint method instead of update I get a compile error, because QDeclarativeItem::paint() is virtual

    Yeah it is not supposed to be called by user. It is called when a re-paint is requested using update. But since QGraphicsProxyWidget is in picture here the re-implementing paint is not required.

    Have you tried to call addFlow from the QML ? This will ensure that the addFlow is called when the FlowGrafik Item is ready.

    157

    ? 1 Reply Last reply
    0
    • p3c0P p3c0

      @Chillax

      But if I call the paint method instead of update I get a compile error, because QDeclarativeItem::paint() is virtual

      Yeah it is not supposed to be called by user. It is called when a re-paint is requested using update. But since QGraphicsProxyWidget is in picture here the re-implementing paint is not required.

      Have you tried to call addFlow from the QML ? This will ensure that the addFlow is called when the FlowGrafik Item is ready.

      ? Offline
      ? Offline
      A Former User
      wrote on last edited by A Former User
      #7

      @p3c0 I created a timer in my QML item, which calls this function periodically:

      void FlowGrafik::refresh()
      {
          qDebug() << "refreshed";
          customPlot->replot();
          customPlot->repaint();
          this->update();
      }
      

      addFlow still gets called from the C++ code periodically and changes the plot values.

      The weird thing is that whatever I write in the constructor of FlowGrafik gets displayed perfectly. I even tried to delete all internal objects of FlowGrafik in the addFlow function, like QGraphicsProxyWidget and customPlot, and I created new ones, but the results are the same. Only the code I write in the constructor gets displayed, and my QML Item never gets updated.

      Could the root of the problem be the fact that I load the QML code from a QmlApplicationViewer?

      main.cpp:

      QmlApplicationViewer flowView;
      flowView.setSource(QUrl("qrc:///qml/qml/FlowView.qml"));
      

      FlowView.qml:

      import QtQuick 1.1
      import FlowGrafik 1.0
      
      Rectangle {
          id: flowGrafik
          objectName: "FlowGrafikRect"
          x: 0
          y: 0
          width: 200
          height: 200
          radius: 10
          Timer {
              interval: 500; running: true; repeat: true
              onTriggered: flowGrafikItem.refresh()
          }
          FlowGrafik {
              id: flowGrafikItem
              objectName: "FlowGrafik"
          }
      }
      
      
      p3c0P 2 Replies Last reply
      0
      • ? A Former User

        @p3c0 I created a timer in my QML item, which calls this function periodically:

        void FlowGrafik::refresh()
        {
            qDebug() << "refreshed";
            customPlot->replot();
            customPlot->repaint();
            this->update();
        }
        

        addFlow still gets called from the C++ code periodically and changes the plot values.

        The weird thing is that whatever I write in the constructor of FlowGrafik gets displayed perfectly. I even tried to delete all internal objects of FlowGrafik in the addFlow function, like QGraphicsProxyWidget and customPlot, and I created new ones, but the results are the same. Only the code I write in the constructor gets displayed, and my QML Item never gets updated.

        Could the root of the problem be the fact that I load the QML code from a QmlApplicationViewer?

        main.cpp:

        QmlApplicationViewer flowView;
        flowView.setSource(QUrl("qrc:///qml/qml/FlowView.qml"));
        

        FlowView.qml:

        import QtQuick 1.1
        import FlowGrafik 1.0
        
        Rectangle {
            id: flowGrafik
            objectName: "FlowGrafikRect"
            x: 0
            y: 0
            width: 200
            height: 200
            radius: 10
            Timer {
                interval: 500; running: true; repeat: true
                onTriggered: flowGrafikItem.refresh()
            }
            FlowGrafik {
                id: flowGrafikItem
                objectName: "FlowGrafik"
            }
        }
        
        
        p3c0P Offline
        p3c0P Offline
        p3c0
        Moderators
        wrote on last edited by
        #8

        @Chillax Did you check by adding the code which changes plot values (same as addFlow) inside refresh ?

        157

        1 Reply Last reply
        0
        • ? A Former User

          @p3c0 I created a timer in my QML item, which calls this function periodically:

          void FlowGrafik::refresh()
          {
              qDebug() << "refreshed";
              customPlot->replot();
              customPlot->repaint();
              this->update();
          }
          

          addFlow still gets called from the C++ code periodically and changes the plot values.

          The weird thing is that whatever I write in the constructor of FlowGrafik gets displayed perfectly. I even tried to delete all internal objects of FlowGrafik in the addFlow function, like QGraphicsProxyWidget and customPlot, and I created new ones, but the results are the same. Only the code I write in the constructor gets displayed, and my QML Item never gets updated.

          Could the root of the problem be the fact that I load the QML code from a QmlApplicationViewer?

          main.cpp:

          QmlApplicationViewer flowView;
          flowView.setSource(QUrl("qrc:///qml/qml/FlowView.qml"));
          

          FlowView.qml:

          import QtQuick 1.1
          import FlowGrafik 1.0
          
          Rectangle {
              id: flowGrafik
              objectName: "FlowGrafikRect"
              x: 0
              y: 0
              width: 200
              height: 200
              radius: 10
              Timer {
                  interval: 500; running: true; repeat: true
                  onTriggered: flowGrafikItem.refresh()
              }
              FlowGrafik {
                  id: flowGrafikItem
                  objectName: "FlowGrafik"
              }
          }
          
          
          p3c0P Offline
          p3c0P Offline
          p3c0
          Moderators
          wrote on last edited by p3c0
          #9

          @Chillax After having a quick look at the QCustomPlot's API, I found QCustomPlot has toPainter method which accepts a QCPPainter as an argument. This QCPPainter in turn accepts a QPaintDevice argument which can be a QImage or QPixmap which means the QCustomPlot can be rendered onto an image or pixmap.
          So after rendering this QCustomPlot's data into an image/pixmap you can periodically call update and re-paint this image/pixmap inside the re-implemented paint method and which will definitely updated on the QML side.

          157

          ? 1 Reply Last reply
          0
          • p3c0P p3c0

            @Chillax After having a quick look at the QCustomPlot's API, I found QCustomPlot has toPainter method which accepts a QCPPainter as an argument. This QCPPainter in turn accepts a QPaintDevice argument which can be a QImage or QPixmap which means the QCustomPlot can be rendered onto an image or pixmap.
            So after rendering this QCustomPlot's data into an image/pixmap you can periodically call update and re-paint this image/pixmap inside the re-implemented paint method and which will definitely updated on the QML side.

            ? Offline
            ? Offline
            A Former User
            wrote on last edited by A Former User
            #10

            @p3c0 Thank you so much for the tip! We are getting really close!
            So I reimplemented the paint method of my custom QDeclarativeItem, FlowGrafik, like this:

            void FlowGrafik::paint(QPainter* painter)
            {
                if (customPlot)
                {
                    qDebug() << "paint";
                    QPixmap picture(200,200);
                    QCPPainter qcpPainter(&picture);
            
                    customPlot->replot();
                    customPlot->toPainter(&qcpPainter);
            
                    painter->drawPixmap(QPoint(), picture);
                }
            }
            

            Unfortunately the results are the same, but I found out that the paint method never gets called! (I didn't see the "paint" at the application output). I tried calling it in the refresh() function like this: this->paint(new QPainter);, and then I saw the "paint" at the application output, but the graph still did not replot. Any ideas on how to move on?

            p3c0P 1 Reply Last reply
            0
            • ? A Former User

              @p3c0 Thank you so much for the tip! We are getting really close!
              So I reimplemented the paint method of my custom QDeclarativeItem, FlowGrafik, like this:

              void FlowGrafik::paint(QPainter* painter)
              {
                  if (customPlot)
                  {
                      qDebug() << "paint";
                      QPixmap picture(200,200);
                      QCPPainter qcpPainter(&picture);
              
                      customPlot->replot();
                      customPlot->toPainter(&qcpPainter);
              
                      painter->drawPixmap(QPoint(), picture);
                  }
              }
              

              Unfortunately the results are the same, but I found out that the paint method never gets called! (I didn't see the "paint" at the application output). I tried calling it in the refresh() function like this: this->paint(new QPainter);, and then I saw the "paint" at the application output, but the graph still did not replot. Any ideas on how to move on?

              p3c0P Offline
              p3c0P Offline
              p3c0
              Moderators
              wrote on last edited by
              #11

              @Chillax As said earlier to call paint you need to call update. So what you can do is call a C++ function from QML periodically which will update the plot values and then call update.

              157

              ? 1 Reply Last reply
              0
              • p3c0P p3c0

                @Chillax As said earlier to call paint you need to call update. So what you can do is call a C++ function from QML periodically which will update the plot values and then call update.

                ? Offline
                ? Offline
                A Former User
                wrote on last edited by
                #12

                @p3c0 Yes, I call update periodically, but that does not call paint

                void FlowGrafik::refresh()
                {
                    qDebug() << "refresh";
                    customPlot->replot();
                    customPlot->repaint();
                    this->update();
                }
                

                I see "refresh" at the application output, but I don't see "paint". The question is why doesn't update call paint?

                p3c0P 1 Reply Last reply
                0
                • ? A Former User

                  @p3c0 Yes, I call update periodically, but that does not call paint

                  void FlowGrafik::refresh()
                  {
                      qDebug() << "refresh";
                      customPlot->replot();
                      customPlot->repaint();
                      this->update();
                  }
                  

                  I see "refresh" at the application output, but I don't see "paint". The question is why doesn't update call paint?

                  p3c0P Offline
                  p3c0P Offline
                  p3c0
                  Moderators
                  wrote on last edited by p3c0
                  #13

                  @Chillax It should actually.
                  http://doc.qt.io/qt-4.8/qgraphicsitem.html#painting

                  Depending on whether or not the item is visible in a view, the item may or may not be repainted

                  Well I guess the Item is visible.

                  157

                  ? 1 Reply Last reply
                  0
                  • p3c0P p3c0

                    @Chillax It should actually.
                    http://doc.qt.io/qt-4.8/qgraphicsitem.html#painting

                    Depending on whether or not the item is visible in a view, the item may or may not be repainted

                    Well I guess the Item is visible.

                    ? Offline
                    ? Offline
                    A Former User
                    wrote on last edited by
                    #14

                    @p3c0 FML :D The item is indeed visible. But it didn't help to hide it before the update and then show it again.

                    I saved the pixmap to a jpg file, and it looks just as I expect it to look like. So the problem is that the QML won't repaint the QDeclaretiveItem, because it is visible... Can you think of a better solution for displaying my QCustomPlot Qwidget? I am pretty sure this is possibe in QML, and it shouldn't be this hard.

                    p3c0P 1 Reply Last reply
                    0
                    • ? A Former User

                      @p3c0 FML :D The item is indeed visible. But it didn't help to hide it before the update and then show it again.

                      I saved the pixmap to a jpg file, and it looks just as I expect it to look like. So the problem is that the QML won't repaint the QDeclaretiveItem, because it is visible... Can you think of a better solution for displaying my QCustomPlot Qwidget? I am pretty sure this is possibe in QML, and it shouldn't be this hard.

                      p3c0P Offline
                      p3c0P Offline
                      p3c0
                      Moderators
                      wrote on last edited by
                      #15

                      @Chillax

                      So the problem is that the QML won't repaint the QDeclaretiveItem, because it is visible...

                      No. It's useless painting invisible objects.

                      Can you try following ?

                      • On the QML side specify width and height for FlowGrafik item. May be this could be the reason the item is not painted i.e having width and height as 0 is close to having an invisible item.

                      • Create a very minimal project with QDeclarativeItem and without using QCustomPlot and keeping rest the same. This is to make sure if paint method is invoked atleast in this case. I dont have Qt 4.8 at hand so I can't test. Have moved to Qt5 long time back :)

                      157

                      ? 1 Reply Last reply
                      0
                      • p3c0P p3c0

                        @Chillax

                        So the problem is that the QML won't repaint the QDeclaretiveItem, because it is visible...

                        No. It's useless painting invisible objects.

                        Can you try following ?

                        • On the QML side specify width and height for FlowGrafik item. May be this could be the reason the item is not painted i.e having width and height as 0 is close to having an invisible item.

                        • Create a very minimal project with QDeclarativeItem and without using QCustomPlot and keeping rest the same. This is to make sure if paint method is invoked atleast in this case. I dont have Qt 4.8 at hand so I can't test. Have moved to Qt5 long time back :)

                        ? Offline
                        ? Offline
                        A Former User
                        wrote on last edited by
                        #16

                        @p3c0 Unfortunately specifying with and height did not solve the issue.

                        I created a minimal project (with QtQuick Application template). It is using QCustomPlot and everything works fine. But this is a Desktop version, and if I am not mistaken it is using Qt 5.3, but I need it to work on my embedded linux Qt 4.8 version.
                        The embedded linux version uses qmlapplicationviewer to load QML files with this comment on top:

                        # This file was generated by the Qt Quick Application wizard of Qt Creator.
                        # The code below adds the QmlApplicationViewer to the project and handles the
                        # activation of QML debugging.
                        

                        the desktop version uses qtquickapplicationviewer:

                        # This file was generated by the Qt Quick 1 Application wizard of Qt Creator.
                        # The code below adds the QtQuick1ApplicationViewer to the project.
                        

                        I'm not sure if the applicationviewer or the qt version difference causes my problem.

                        p3c0P 1 Reply Last reply
                        0
                        • ? A Former User

                          @p3c0 Unfortunately specifying with and height did not solve the issue.

                          I created a minimal project (with QtQuick Application template). It is using QCustomPlot and everything works fine. But this is a Desktop version, and if I am not mistaken it is using Qt 5.3, but I need it to work on my embedded linux Qt 4.8 version.
                          The embedded linux version uses qmlapplicationviewer to load QML files with this comment on top:

                          # This file was generated by the Qt Quick Application wizard of Qt Creator.
                          # The code below adds the QmlApplicationViewer to the project and handles the
                          # activation of QML debugging.
                          

                          the desktop version uses qtquickapplicationviewer:

                          # This file was generated by the Qt Quick 1 Application wizard of Qt Creator.
                          # The code below adds the QtQuick1ApplicationViewer to the project.
                          

                          I'm not sure if the applicationviewer or the qt version difference causes my problem.

                          p3c0P Offline
                          p3c0P Offline
                          p3c0
                          Moderators
                          wrote on last edited by
                          #17

                          @Chillax
                          qtquickapplicationviewer was a helper class added back then which calls other in-built functions to load QML files. It also provided some extra functions for ease. You can also directly use QQuickView or QQmlApplicationEngine to load the QML files depending upon the root object. This is all Qt 5.x related.
                          Similarly qmlapplicationviewer is an helper class. If you look into its source you can see it is actually subclassed from QDeclarativeView which actually loads and displays the QML files.

                          I'm not sure if the applicationviewer or the qt version difference causes my problem.

                          AFAIK definitely not applicationviewer but may be Qt version.

                          Also did you try running same application with Qt 4.8 on desktop ? I think you should try that too to rule out the system problem if any.

                          157

                          ? 2 Replies Last reply
                          0
                          • p3c0P p3c0

                            @Chillax
                            qtquickapplicationviewer was a helper class added back then which calls other in-built functions to load QML files. It also provided some extra functions for ease. You can also directly use QQuickView or QQmlApplicationEngine to load the QML files depending upon the root object. This is all Qt 5.x related.
                            Similarly qmlapplicationviewer is an helper class. If you look into its source you can see it is actually subclassed from QDeclarativeView which actually loads and displays the QML files.

                            I'm not sure if the applicationviewer or the qt version difference causes my problem.

                            AFAIK definitely not applicationviewer but may be Qt version.

                            Also did you try running same application with Qt 4.8 on desktop ? I think you should try that too to rule out the system problem if any.

                            ? Offline
                            ? Offline
                            A Former User
                            wrote on last edited by
                            #18

                            @p3c0 So I spent the last couple of hours trying to find out how to install Qt version 4.8 on Ubuntu, but it turns out that only the versions newer than 5.0 support linux. So I installed Qt Creator and Qt version 4.8 on Windows and it works there as well :)

                            1 Reply Last reply
                            0
                            • p3c0P p3c0

                              @Chillax
                              qtquickapplicationviewer was a helper class added back then which calls other in-built functions to load QML files. It also provided some extra functions for ease. You can also directly use QQuickView or QQmlApplicationEngine to load the QML files depending upon the root object. This is all Qt 5.x related.
                              Similarly qmlapplicationviewer is an helper class. If you look into its source you can see it is actually subclassed from QDeclarativeView which actually loads and displays the QML files.

                              I'm not sure if the applicationviewer or the qt version difference causes my problem.

                              AFAIK definitely not applicationviewer but may be Qt version.

                              Also did you try running same application with Qt 4.8 on desktop ? I think you should try that too to rule out the system problem if any.

                              ? Offline
                              ? Offline
                              A Former User
                              wrote on last edited by
                              #19

                              @p3c0 Interesting news: Until now, my QmlApplicationViewer flowView was just a new window on top of the GUI I was using until now. But if I show only flowView in fullscreen and nothing else, it works (updates/repaints).

                              qmlRegisterType<FlowGrafik>("FlowGrafik",1,0,"FlowGrafik");
                              QmlApplicationViewer flowView;
                              flowView.setSource(QUrl("qrc:///qml/qml/FlowView.qml"));
                              flowView.showFullScreen();
                              
                              ? 1 Reply Last reply
                              1
                              • ? A Former User

                                @p3c0 Interesting news: Until now, my QmlApplicationViewer flowView was just a new window on top of the GUI I was using until now. But if I show only flowView in fullscreen and nothing else, it works (updates/repaints).

                                qmlRegisterType<FlowGrafik>("FlowGrafik",1,0,"FlowGrafik");
                                QmlApplicationViewer flowView;
                                flowView.setSource(QUrl("qrc:///qml/qml/FlowView.qml"));
                                flowView.showFullScreen();
                                
                                ? Offline
                                ? Offline
                                A Former User
                                wrote on last edited by
                                #20

                                @p3c0 What's more interesting: If I call addFlow from QML, it works (replots). But if I call it from C++, it updates the QWidget, but not the QML Item. Even if I call refresh() from QML right after it, which should replot and repaint the QML Item too. Any explanation to this? Why is there a difference between changing the QWidget in the C++ code and asking for a replot from QML and doing everything in QML? As if the QML Item and the C++ QDeclarativeItem were two independent objects.

                                So now my plan is to give the flow value from C++ to the FlowGrafik QML item, and then call addFlow from QML. That should work.

                                p3c0P 1 Reply Last reply
                                0
                                • ? A Former User

                                  @p3c0 What's more interesting: If I call addFlow from QML, it works (replots). But if I call it from C++, it updates the QWidget, but not the QML Item. Even if I call refresh() from QML right after it, which should replot and repaint the QML Item too. Any explanation to this? Why is there a difference between changing the QWidget in the C++ code and asking for a replot from QML and doing everything in QML? As if the QML Item and the C++ QDeclarativeItem were two independent objects.

                                  So now my plan is to give the flow value from C++ to the FlowGrafik QML item, and then call addFlow from QML. That should work.

                                  p3c0P Offline
                                  p3c0P Offline
                                  p3c0
                                  Moderators
                                  wrote on last edited by
                                  #21

                                  @Chillax Unfortunately I too dont understand this behavior. The fact that it works in desktop environment and not on embedded only points that there should be some bug in that environment.

                                  So now my plan is to give the flow value from C++ to the FlowGrafik QML item, and then call addFlow from QML.

                                  Try. I had suggested the same earlier :)
                                  Let us know if it works or if possible the exact reason so that it may help others too.

                                  157

                                  ? 1 Reply Last reply
                                  0
                                  • p3c0P p3c0

                                    @Chillax Unfortunately I too dont understand this behavior. The fact that it works in desktop environment and not on embedded only points that there should be some bug in that environment.

                                    So now my plan is to give the flow value from C++ to the FlowGrafik QML item, and then call addFlow from QML.

                                    Try. I had suggested the same earlier :)
                                    Let us know if it works or if possible the exact reason so that it may help others too.

                                    ? Offline
                                    ? Offline
                                    A Former User
                                    wrote on last edited by
                                    #22

                                    @p3c0 So thanks a lot for the help! I would have given up without you :) The problem was that I created two instances of FlowGrafik. One in the QML and one in C++. I changed the C++ one and expected the QML one to refresh.

                                    Now I created a pointer in the C++ code that points to the Item in the QML.

                                    QmlApplicationViewer flowView;
                                    flowView.setSource(QUrl("qrc:///qml/qml/FlowView.qml"));
                                    QObject * flowViewObject = flowView.rootObject();
                                    FlowGrafik * flowGrafik = flowViewObject->findChild<FlowGrafik *>(QString("FlowGrafik"));
                                    

                                    But now if I want to use this pointer (like flowGrafik->addFlow(...)) I get a segmentation fault. Do you know why?

                                    p3c0P 1 Reply Last reply
                                    0
                                    • ? A Former User

                                      @p3c0 So thanks a lot for the help! I would have given up without you :) The problem was that I created two instances of FlowGrafik. One in the QML and one in C++. I changed the C++ one and expected the QML one to refresh.

                                      Now I created a pointer in the C++ code that points to the Item in the QML.

                                      QmlApplicationViewer flowView;
                                      flowView.setSource(QUrl("qrc:///qml/qml/FlowView.qml"));
                                      QObject * flowViewObject = flowView.rootObject();
                                      FlowGrafik * flowGrafik = flowViewObject->findChild<FlowGrafik *>(QString("FlowGrafik"));
                                      

                                      But now if I want to use this pointer (like flowGrafik->addFlow(...)) I get a segmentation fault. Do you know why?

                                      p3c0P Offline
                                      p3c0P Offline
                                      p3c0
                                      Moderators
                                      wrote on last edited by
                                      #23

                                      @Chillax Thank you :)

                                      The problem was that I created two instances of FlowGrafik. One in the QML and one in C++. I changed the C++ one and expected the QML one to refresh.

                                      but now this makes me wonder as to why it worked on desktop.

                                      But now if I want to use this pointer (like flowGrafik->addFlow(...)) I get a segmentation fault. Do you know why?

                                      Was the FlowGrafik object found ? You can add a small condition to verify it.

                                      if(flowGrafik) {
                                         flowGrafik->addFlow(...)
                                      }
                                      

                                      157

                                      ? 1 Reply Last reply
                                      0
                                      • p3c0P p3c0

                                        @Chillax Thank you :)

                                        The problem was that I created two instances of FlowGrafik. One in the QML and one in C++. I changed the C++ one and expected the QML one to refresh.

                                        but now this makes me wonder as to why it worked on desktop.

                                        But now if I want to use this pointer (like flowGrafik->addFlow(...)) I get a segmentation fault. Do you know why?

                                        Was the FlowGrafik object found ? You can add a small condition to verify it.

                                        if(flowGrafik) {
                                           flowGrafik->addFlow(...)
                                        }
                                        
                                        ? Offline
                                        ? Offline
                                        A Former User
                                        wrote on last edited by
                                        #24

                                        @p3c0 You are right, it was not found, because it was actually the rootobject, not a child :) Thanks again for the help!

                                        p3c0P 1 Reply Last reply
                                        0
                                        • ? A Former User

                                          @p3c0 You are right, it was not found, because it was actually the rootobject, not a child :) Thanks again for the help!

                                          p3c0P Offline
                                          p3c0P Offline
                                          p3c0
                                          Moderators
                                          wrote on last edited by
                                          #25

                                          @Chillax You're Welcome :)

                                          157

                                          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