Community
Participate
Working Groups
Should WorkbenchPartReference make use of IsaveableModelSource. It seems that it should so that handling of dirty determination for a part will be consistent. That is, the Save action ignores the isDirty of the part when issuing saves whereas the reference makes use of it. Perhaps this is intentional to separate the dirty decoration of a part tab (in my case, an editor) from the save behavior. If that is so, it needs to be well documented.
For now, I'm intentionally leaving it up to the part to communicate its own dirty state, taking into account the models it presents if needed. There may be cases where a view wants to work in terms of models, but not show a dirty flag even if the models are dirty.
No plans to change this for 3.2.
