|SaveAllAction NonPartSourcs [message #645009]
||Wed, 15 December 2010 08:39
| Ronald Krijgsheld
Registered: November 2010
I try to understand the concepts behind the interfaces ISaveable and the NonPartSources.
I checked the implementation of the SaveAllAction and found the following.
1. the updateState() method checks if there are dirty saveables in the registered NonPartSources to decide whether or not the action is enabled.
2. the run() method delegates to the editormanager to execute a saveAll(). This method is implemented to do nothing if there are no dirty editparts.
3. the updateState() is triggered based on changes in parts.
How is it possible with this implementation to get a nonpartsource correctly working? All variations I tried at some point need an edit part to trigger the logic.
The use case I have is simple. I have multiple explorers based on one model. If I make change in a propertysheet I like to have the save all button enabled.
The NonPartSource concept suggested that I could register saveables that are independent of edit parts.
But it looks like I have to make all explorers saveableparts. But that kind of defeats the purpose of a NonPartSource.
any pointers, ideas on this?
Powered by FUDForum
. Page generated in 0.01486 seconds