In our system users can make changes to the diagram at will - adding nodes and links and moving both within the diagram.

We automatically save the diagram, in the background, after each change, then reload the saved diagram (so we get ids for nodes etc. to use when adding links)

However, if a large background image (4.5 megabytes) is used for the diagram this save takes some time and the user can make changes whilst the save is taking place which then 'disappear' when the diagram is reloaded.

A possible solution would appear to be to remove the background image from the diagram before saving it, then put it back after the save. However, this causes the diagram to be displayed with a blank background for a significant period of time. From stepping through my code it seems to be the call to Diagram.saveToXml(document) which causes the 'backgroundless' diagram to be displayed.

Is there anyway of stopping this happening?

Or can you think of an alternative method which would allow saving all changes in the background, but would not 'loose' any changes made by the user during the time taken for the save.

Could you let me know when you make the official release with Diagram.updateRuntimeIndices() as a public method please.

(We're only using these values very short term, not assuming they remain the same long term)