Hey guys, I've decided that the work involved in transitioning to QAbstractItem* is overwhelming and might cause me to miss my deadlines. It's possibly something for a 2.0 (assuming QAbstractItem* it is a better suited solution).
For reference, here are some of the things consuming time. I couldn't figure out how to get QAbstractItemModel to work without involving QModelIndexes, which is ok. However, QAbstractItem*View* is also dependent on QModelIndex, which means deriving anything custom would involve adapting QModelIndex here as well, not to mention its separation between selection models and delegates. Overall, it is my impression that the QAbstractItem* family is designed to enable very large data models, which isn't what I'm looking for. As I've built my views and have a working prototype, I can either get with it or tear it down and start over, which like I said would put my schedule at risk. Not sure what you guys would do, but to me it seems a perfectionist issue (again, assuming QAbstractItemModel is the perfect candidate) Thoughts? -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmODzSVxGxxgB2BKitoKs3_itn9N5dizRWdi7%2BmYwMHuFAQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
