Quote Originally Posted by MattPhillips View Post
I guess I hadn't expected this to be a property of the model, but rather the view, since you could conceivably want an item editable in one view but not editable in another.
Hmm, yes that could be the case. However, the model specifies whether an item is inherently editable. If you would want to block certain views from editing the item you could always use either a proxy model that strips the editable flag, or use a delegate that doesn't allow editing. In any case, the model/view framework has been designed in a way that changes through one view are (practically) immediately reflected in all other views. And well, if you run into such a situation, maybe it is time to reconsider your design (which is a good thing to do in any case)...