jordi fita mas
94b5faa9d8
I have my doubts whether this model should be QAbstractListModel-derived or not. At first i thought i could not be, because i need to be able to get a “view” (i.e., a [begin, end) pair of iterators) based on the segment of TimelineView that becomes exposed due to scroll. However, QAbstractItemModel::match returns a QModelIndexList, and that could also be used for the same purpose, except that there is no QDateRange…. Until i have more needs for this model, the current coupling between TimelineModel and TimelineView is OK, as i do not expect TimelineView to be used for anything else. I also renamed CalendarModel to TimelineListModel, since this is the important part—the timeline—, and there is no “calendar” thing anywhere in the application—at least, not what traditionally is understood as a calendar, that is.