https://bugs.kde.org/show_bug.cgi?id=420533
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@kde.org
Status|REPORTED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #1 from Nate Graham <n...@kde.org> ---
We changed this behavior because people would open the image in the external
app, make some changes, and then one or both of the following things would
happen:
1. If the system temp folder was not writable by their user, they would get an
error message when they tried to save the image.
2. If they closed the program without first saving the image in a different
location using "Save As...", they would be unable to locate the image.
I think the ideal solution here would be to keep saving to a temp folder, but
somehow make the app not able to re-save the image in the current location and
always prompt the user to "Save As..." in another location. I'm not sure if
that's technically possible though.
For your workflow, I believe you could just set the default save folder to be
/tmp/ (or wherever), and then screenshots would be saved to a hidden hidden
location that gets cleaned up automatically just like you want.
--
You are receiving this mail because:
You are watching all bug changes.
