The delegate is provided once per view using the "delegate" property of the view. The model itself doesn't use a delegate.
No, that's wrong, that's my point that you are doing it the wrong way. Your model shouldn't be composed of delegates or anything like that. The model holds data, regardless of how the data is stored. You don't need any "items" in the model, the data could be generated on the fly. The "items" are not "delegates", they have no visual representation in the model.this might be set via setItemData() correct? And in the delegate I can access the data via the role.
The way I see it you are providing a custom delegate (TaskData or EmpData). If you implement it in C++, it will be derived from QDeclarativeItem.What for do i need the QDeclarativeItem anyways?
You have QDeclarativeItem instances all over your code, just take a look.By now it is working without it..
Different model instances of what?If i store the data in the model directly i have to use different model instances
The model doesn't interact with data. The model represents the data, it provides access to it.how does the model interact with that Data?






Reply With Quote
Bookmarks