If you open an archive with read/write permissions, then change the open or closed state of workspaces, libraries, desktops, folders, reel groups, reels etc then flame will interpret this as a change to the state of the archive and re-write the header.
Thanks…I don’t want it to re-write the header…. Is there an option to not re-write the header? If not there should be.
Because most of the time I’m just looking through an archive for something and I have to open up folders to look at them….but if I don’t find it then I want it to close without re-writing the header.
I have had that experience on v2025 and earlier. I don’t have the same issue on 2026. It doesn’t seem to matter if it is read only or read/write. v2026.1 on Linux