Quote Originally Posted by jpn
See QStandardItemModel::setItem(int row, int column, QStandardItem* item). Notice the column parameter.
A couple problems with this:
  1. During construction, there is no parent model.
  2. There is no slot or virtual function that is triggered when the Item is attached to a model, so delaying construction of that item is not an option.


True, I could pass the parent to the constructor, insert it manually (Which row?), create the QStandardItem for the second item of the top column for Description, and set Description as a child or sibling of the main item. At that point, I might as well go back to the basic QAbstractModel, and would lose the modularity that I am trying to get by using QStandardItem in the first place.