Temporary "mark" for session files #42
Replies: 3 comments 2 replies
|
Hi, |
|
...oopsie - ah, I missed that 😅 thank you for pointing it out; close this for now. |
|
@houmain So yes, disabling or preventing these save dialogs for dynamically created/modified files per group sounds like a very good idea 😌 |
Uh oh!
There was an error while loading. Please reload this page.
It would be very useful to have a way to mark certain files (e.g., external/script/action-generated) as "temporary" alike, so they are not treated as modified within a session.
Currently, such files are detected as changed/new and included in the automatic "Save As..." flow, which adds unnecessary chore-noise.
A possible solution would be a dedicated flag or checkbox (e.g., "temporary", "cache", or "volatile" - up to you).
Files marked this way would be excluded from save prompts and session change tracking.
...in my current workflow, I often use a mix of offline-prepared files and files generated via scripting or actions.
Having to manually omit them each time they appear as modified in the "Save As..." dialog becomes tedious.
All reactions