Hi all, I just want to know if that's a sensible thing to do. Well, I have a working QStandardItemModel in my app, that has a tree view in the main window to provide simple navigation. Then I found myself in need to wrap the existing navigation tree in another tree, ie to show the current top-level items as children to a new top-level item. I've been trying to do this by wrapping the existing QStandardItemModel in a new QAbstractItemModel subclass, using the latter's model indexes as objects internalPointer() points to. And I keep crashing my app for the last several hours :-( So, is this a used approach at all? If there's something fundamentally wrong about it, I guess I'd better off building a brand new QAbstractItemModel from scratch.
Thanks in advance.
_______________________________________________ PySide mailing list [email protected] http://lists.pyside.org/listinfo/pyside
