mirror of
https://github.com/OrcaSlicer/OrcaSlicer.git
synced 2026-10-13 10:51:12 +00:00
Hanif Koh
2063f0b2a7
The lock guard is meant for a few file operations, and zipping a large user folder is not one, so the backup is taken before it and the guard covers the writes only; each write re-reads its file, so a save that slipped in before is still respected. The in-memory update adds the lost printers to the list the preset holds at that moment rather than replacing it with the one found at detection, and leaves a pending cloud sync state alone: a download waiting to be saved kept its newer list and its "save" flag, which "update" would have cancelled. The lock message no longer blames another instance alone, since the lock is also refused for a while after a miss and when the lock file cannot be opened.