You can create custom views if you want. See the Chart Example

Hello, Thanks a lot for the replies. I found out another way by which we can hide the 'section' if the parent doesn't have any childrens. ui.treeView->setRowHidden(parentRow, rootIndex, true) In my example, Fruits - ............Apple ............Orange Animals - .............Lion .............Tiger Colors - ............Red ............Green ............BLue Fruits is 0th parent Animals is 1st parent Colors is the 2nd parent So whenever any of the children's are missing ( which we come to know while filling up the model ), I am setting the respective "parent" row as hidden. This approach worked fine and as expected. Is anything wrong with this approach? Model remains the same, only the view is hidden or unhidden based on some condition. Please Let me know.

Waiting for guide "How to avoid JavaScript models in Qt and why should you care" (performance, memory usage)

@VRonin That's really useful, thank you very much. Also I didn't know about the "Model test", that's nice too.

thanks. i will try it :)

I have posted suggestion about adding such positioner to QtQuick: https://bugreports.qt.io/browse/QTBUG-57549

http://www.qtcentre.org/threads/66403-How-to-get-Object-s-pointer-instantiated-in-QML-engine?p=291959#post291959

Yeah but the user also want to be able to reorder things as he wants, not just sort (ie, put this row here, drag all my selection at this position, invert these two rows, ...)

@tokafr if i got you correct you want to drag&drop from your Qt application to the filesystem? If so take a look here.

@p3c0 said: @Kofr So is it that you want to access the roles (namely hue, saturation, brightness) values from outside of this ListView delegate ? If so then did you accessing ListVIew model from outside ? Once you get hold of it the data can be accessed too. code above is just example, not my case. what I need is to get model.roleName of delegate j when I work in delegate i

Hi, You can try with the QHeaderView::minimumSectionSize property

@Rohith A controller is simply an object that controls both the model and the view. The following brief example should get you started: class MyController : public QObject { Q_OBJECT public: MyController(QObject * parent = NULL) : QObject(parent) { view.setModel(&model); } int exec() { view.show(); return QApplication::exec(); } private: // ... QTreeView view; QFileSystemModel model; }; And you use simply by creating the object and invoking the appropriate method(s). int main(int argc, char ** argv) { QApplication app(argc, argv); MyController controller; return controller.exec(); } @asanka424 However in my experiece, MVC cannot be implemented as cleanly as in a web application for a desktop application. Main reasone is that all UI widgets have some sort of controller embedded in already. For that reason Qt has something called Model-View architecture which is not the MVC pattern but something similar to de-couple your data from the view. Qt only applies the view as controller, but doesn't actually "require" the user programmer to follow. The same effect as and I'd say better could be obtained by separating the logic. One thing that springs to mind: no need to derive a whole class only to have a form initialized in the constructor. The only problem with MVC is that it's used with and without reason (as all "architectural" and "design" patterns are), because people are mislead to believe them as one size fits all solution. Kind regards.

Viele danke Herr Sam :)

Hi, There's no ready made code to dump your model since only you know what make sense to dump. So yes you'll have to write the dumper and loader yourself. QDataStream comes to mind for that task. Hope it helps

@CoderJeff Oh. Sorry, I thought its other way. Didn't understood what you meant here.

No problem ! That's probably because they are not enabled, check your account settings for that.