On several occasions, I ran into problems very similar to jwombie's. I always wondered how to use QAIM correctly. (Side note: unfortunately, Qt's design isn't helpful here: there are Qt models that are adapters ( e.g. QSqlTableModel) and Qt models that are data stores (e.g. QStringListModel))

I always tended to create adapter models that provide a view into my data, however that may be stored. But then I quickly ran into problems. I would not be able to tell what models to notify if the underlying data had changed. A google search suggested that I was doing it wrong and I should just use one big QAIM to avoid synchronization problems :-(

So my question is: if a QAIM is best used as an adapter, is there any "recommended practice" how to synchronize models?
I'm afraid of using a single, huge QAIM. Trying to squeeze all of my data into a hierarchical table would quickly become ugly (I tried. I gave up).

Thanks
Markus

You should see the item models are merely an interface to your data, but they should not be the data object. Take a look at "this more detailed explanation":http://developer.qt.nokia.com/doc/qt-4.7/model-view-programming.html#note-13 that I wrote down in the documentation.