https://bugs.kde.org/show_bug.cgi?id=395774
Victor Wåhlström <victor.wahlst...@initiali.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |victor.wahlstrom@initiali.s
| |e
--- Comment #4 from Victor Wåhlström <victor.wahlst...@initiali.se> ---
While "Export" would avoid this problem entirely, I don't think the original
report is without merit.
I'm not sure everyone is aware of the difference between "Save As" and
"Export", and what they do exactly. Given that "Save As" is pretty consistent
across applications and "Export" might not even exist, it's easy to default to
the familiar "Save As" even though "Export" is what you want.
Since the data in the current session is not immediately lost when you save to
a different format, you can simply recover from a "Save As: PNG" situation by
using "Save As" again and save to KRA.
The real problem is that once you use "Save As", Krita clears the dirty state,
allowing for the following scenario:
1. Create a new document
2. Draw something
3. Save as KRA
4. Continue working
5. Save as PNG
6. Close Krita
7. Krita won't warn you about unsaved changes, discarding all work done in step
4.
Sure, you still have the PNG file, but that's missing a bunch of data.
One way to avoid this scenario is to have Krita keep track of the last time you
saved the current session as KRA, separately from the internal dirty state.
This way, Krita knows that there are "unsaved" changes when you close the
document, despite having just saved it to PNG.
--
You are receiving this mail because:
You are watching all bug changes.
