|
|
<snip, QAbstractItemModel hard to understand>
Benjamin Meyer responded:
>Sorry to hear it was so difficult. Sense 4.0 I have gone through most of the
>docs improving things that I could. <snip>,
>I have been monitoring this list and when I see the same question asked
>several times I try to improve the docs so that question is easier to find.
> <snip>,
Does TrollTech have thoughts about the discussion on the
QModelIndex, like responses to the questions at the bottom of
the thread:
<http://lists.trolltech.com/qt-interest/2006-11/thread00662-1.html>
In this current thread, I agree that the model/view is a complicated
design, but necessarily so because it's a complicated problem.
I like that the design provides resonable default implementation,
and merely requires implemenation of only a few functions in
most cases.
In the end, I view it as a powerful-and-flexible adapter layer between
the the application-specific model and the interface. Yes, you
have to study the design to use it effectively (I agree with the
previous statement in this thread that this is the most complicated
design in the Qt libraries).
My only real "wish" relates to adding "type" information to the
QModelIndex. ;-) Any thoughts there?
--charley
____________________________________________________________________________________
Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index
--
To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
"unsubscribe" in the subject or the body.
List archive and information: http://lists.trolltech.com/qt-interest/
|
|