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. Exposing C++ model property of type QList<QObject*> to QML
Forum Updated to NodeBB v4.3 + New Features

Exposing C++ model property of type QList<QObject*> to QML

Scheduled Pinned Locked Moved QML and Qt Quick
20 Posts 6 Posters 21.6k 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.
  • J Offline
    J Offline
    joonne
    wrote on last edited by
    #8

    Hi,

    thanks for reply!

    I followed the documentation at this "link":http://qt-project.org/doc/qt-5/qqmllistproperty.html and got it to compile, now the only problem is that I am not sure how I am supposed to update the model and let the QML-side know about changes in the model.

    I have the NOTIFY signal of the Q_PROPERTY in my code; should it work alone or am I supposed to update the model via setContextProperty() as I was trying to do earlier?

    Also I would like to understand better which is better; register the class with qmlRegisterType and then set up the model in QML or use setContextProperty() in main.cpp ? Can I use them both at the same time? I am still a bit confused with these.

    1 Reply Last reply
    0
    • M Offline
      M Offline
      messi
      wrote on last edited by
      #9
      1. Question
        Some where in your C++ model you have to emit the signal function which is connected to your NOTIFY declaration.

      2.Question
      http://qt-project.org/forums/viewthread/13210

      1 Reply Last reply
      0
      • J Offline
        J Offline
        joonne
        wrote on last edited by
        #10

        Hi,

        I now have a new problem or I am a bit confused. This relates to the above posts so I thought I could ask this here.

        I want to make/have started to make an TV-Guide view for my Sailfish/QT5 -application. I have SlideShowView and I use VisualItemModel as model for it. Then I am creating my own Channel-Items to have own page for each channel.

        In the Channel.qml I have SilicaListView and I am trying to use my own C++ and QQmlListProperty-based model for it. So the first question is that is it okay to make a new Model for each Channel-Page's listview?

        The main problem for me is to understand where and how should I initialize the model; in the qml file or in C++? Also I would like to know is it okay to have QList<MyListModel*> and then return the right one for the right tv-channel?

        Here is some code to help to understand my issue:

        @ SlideshowView {
        id: channelView
        width: tvguidepage.width
        height: tvguidepage.height
        itemWidth: width

            model: VisualItemModel {
                id: channels
                Channel {id: tv1 }
                Channel {id: tv2 }
                Channel {id: mtv3 }
            }
        }
        
        function initialize() {
        
            tv1.initialize("Yle TV1");
            tv2.initialize("Yle TV2");
            mtv3.initialize("MTV3");
        
        }@
        

        @property ProgramListModel programlist

        function initialize(channel) {
            // I tried to set the right channel
            dataModel.setDesiredChannel(channel);
            // and then just return it with Q_PROPERTY(READ) 
            listview.model = dataModel.programListModel
            console.log("ProgramListModel" + listview.model) // it isn't null
        }
        
        SilicaListView {
            id: listview
        
            header: Component {
                PageHeader {
                    id: pageheader
                    title: "channel"
                }
            }
        
            anchors.fill: parent
        
            delegate: ListItem {
        
                width: parent.width
        
                Column {
        
                    Label {
                        // role's name from C++
                        text: programName
                    }
        
                    Label {
                        // role's name from C++
                        text: time
        
                    }
                }
            }@
        
        1 Reply Last reply
        0
        • M Offline
          M Offline
          messi
          wrote on last edited by
          #11

          Hi Joonne,

          lately I discussed exact this topic with my friends.
          Our conclusion is this. Use one model for all data.
          With a QAbstractProxyModel you can decide which data should be displayed on which page. Yoou can also add a QAbstractSortModel as well.

          Do the model in C++. Use either QAbstractListModel or QAbstractItemModel.
          Create a QAbstractProxyModel as well.

          Register both modeles in your main.cpp with qmlRegisterType

          Here is a small example:

          @Rectangle {
          property int entriesPerPage: 9
          width: 360
          height: 360

          MyModel { id: mainModel }
          
          ListView {
              id: listView
              width: parent.width
              height:parent.height
              anchors.centerIn: parent
              objectName: "listView"
          
              snapMode: GridView.SnapToRow
              orientation: Qt.Horizontal
          
              model: mainModel.rows/entriesPerPage // Check if this works
          
              delegate:
              Component {
                  Rectangle {
                      id: listItem
                      width: 360
                      height: 360
                      border.color: "blue"
                      border.width: 2
          
                      GridDelegate {
                          width: 300
                          height: 300
          
                          model: MyProxyModel {
                              mySource: mainModel
                              itemsPerPage: entriesPerPage
                              pageNumber: index
                          }
                      }
                  }
              }
          }
          

          }@

          1 Reply Last reply
          0
          • J Offline
            J Offline
            joonne
            wrote on last edited by
            #12

            Thanks for reply!

            I am maybe a little more confused now. :D

            I would like to know if you meant that I should somehow place all the tv-programs as a list to QAbstractListModel and then select the correct ones with QModelIndex with the mapFromSourceFunction() ?

            I just learned how to use the QQmlListProperty model and this seems very complicated.

            1 Reply Last reply
            0
            • M Offline
              M Offline
              messi
              wrote on last edited by
              #13

              Hi Joonne

              yes exactly. You have to implement in your ProxyModel mapFromSource(), mapToSource(), index(), columnCount(), rowCount().

              you mentioned that you are programming a TV-Guide with a SlideShowView.
              So when you have got e.g. 200channels and you like to display 10channels/page then you will have 20 pages to navigate.

              The QAbstractListModel will hold all your channel unsorted (raw).
              Now you can add an extra QAbstractSortModel where you can add your sorting rule e.g. channel number sorting, channel name sorting, favorite sorting etc.
              You can also add a QAbstractProxyModel for filtering.

              With the QAbstractProxyModel you can define how many channel per pages shall be displayed. In my example you will have for each page a ProxyModel.

              I hope my explanation clarifies it better.

              1 Reply Last reply
              0
              • J Offline
                J Offline
                joonne
                wrote on last edited by
                #14

                Okay, thanks again!

                I think I understood what you meant. However my use-case is going to be a little bit different from what you explained.

                One page of the SlideShowView should have all the programs of the channel, so when swiping left/right, you have a new channel and the programs for that channel. I don't know yet how I can achieve this kind of model-structure. Please tell me if I am thinking this all wrong. :)

                1 Reply Last reply
                0
                • J Offline
                  J Offline
                  joonne
                  wrote on last edited by
                  #15

                  Any ideas for this kind of situation?

                  If I make a QAbstractListModel that contains all the episodes of all channels, could I then filter the right ones for the correct page? Could I access the roles of the program-class with the sortmodel ?

                  Thanks in advance :)

                  1 Reply Last reply
                  0
                  • J Offline
                    J Offline
                    joonne
                    wrote on last edited by
                    #16

                    Any ideas for this kind of situation?

                    If I make a QAbstractListModel that contains all the episodes of all channels, could I then filter the right ones for the correct page? Could I access the roles of the program-class with the sortmodel ?

                    Thanks in advance :)

                    1 Reply Last reply
                    0
                    • M Offline
                      M Offline
                      messi
                      wrote on last edited by
                      #17

                      Hi joonne

                      you have two possibilities:
                      1.) Model in model. One for the channel and one model for the channel program
                      With this solution you can easily set the program model to the program list view.

                      2.) Create a TreeModel
                      http://qt-project.org/doc/qt-4.8/itemviews-simpletreemodel.html

                      Both are possible.

                      1 Reply Last reply
                      0
                      • M Offline
                        M Offline
                        messi
                        wrote on last edited by
                        #18

                        Hi joonne

                        you have two possibilities:
                        1.) Model in model. One for the channel and one model for the channel program
                        With this solution you can easily set the program model to the program list view.

                        2.) Create a TreeModel
                        http://qt-project.org/doc/qt-4.8/itemviews-simpletreemodel.html

                        Both are possible.

                        1 Reply Last reply
                        0
                        • J Offline
                          J Offline
                          justin1122
                          wrote on last edited by
                          #19

                          I know this is an old thread, but I had a similar problem to that of the original poster (stas2)

                          I was able to have the QML read the QList properties correctly after using the following syntax in the QML view:

                          @ListView {
                          model: appData.axes
                          delegate: Text { text: model.modelData.name }
                          }@

                          1 Reply Last reply
                          0
                          • J Offline
                            J Offline
                            justin1122
                            wrote on last edited by
                            #20

                            I know this is an old thread, but I had a similar problem to that of the original poster (stas2)

                            I was able to have the QML read the QList properties correctly after using the following syntax in the QML view:

                            @ListView {
                            model: appData.axes
                            delegate: Text { text: model.modelData.name }
                            }@

                            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