The origin of the problem: I have a cml file that includes multiple sessions. Now I want to export each session to a separate core archive. The apparently easiest way to achieve this to

• load the original cml file
• remove all but the first session
• export this session to core archive
• reload the original cml file
• remove all but the second session
• export this session to core archive
• and so on

The created core archives contain

• the image files from the remaining session (as expected)
• the original cml file renamed to session.cml (including also the deleted session)

Corelyzer apparently assumes that the user has saved the session just before the export to core archive. In the workflow above, but also in other situations, this could lead to unwanted results. I suggest to change the export to core archive by either A) explicitly asking the user to save the session before export in a separate dialogue or B) always saving the session to a temporary cml file that then is included in the archive. Preferably B), as it is more flexible (could be extended with a dialogue that lets the user choose the sessions to be included in the core archive).