This wishlist item came from a conversation with some game developers in my area. This is the situation to try to make better. You have a multi layered high res file that you have been working from. You are ready to share it, but need to shrink the image size down a lot by collapsing layers and shrinking the image size. Before exporting it you make some small adjustments like sharpening and curves to help some areas pop. You like the result so you hit Ctrl + S. Result: You just destroyed most of your working image that you have been building up. Pain! Expected: A warning dialog with something like "Your file size has decreased by over 50% since your last save. Are you sure you want to do this?" While someone can easily get past the warning and still lose details from their working file, I think this might help mitigate this situation. Not sure if anyone else comes across this situation when working. It is pretty minor, but a nice UX touch I think.
Are they sharing .kra files, or files exported to PNG?
The end result is probably sharing a PNG or a JPG. It has to do with saving over your existing KRA document. Usually when sharing something online, you need to resize your image to be smaller first. An easy way to do this is to resize your KRA image to make it smaller, then export it as a PNG or JPG. That is where the problem happens. It can be easy to forget that you resized it down to make it smaller. The next time you press "Ctrl + S" to save, your KRA is now much smaller. People that share a lot of artwork online might be able to understand what this is. Not sure if they could explain the situation better than I am doing.
Wouldn't be better to just implement bug 397172 and bug 388412 instead? It seems like they "temporarily destroy" their images and want to be warned if they accidentally try to save it to the original, not-destroyed version of the file. Maybe it would be better create an easy workflow that achieves this without destroying the documents in the first place.
Yes. I think that would take care of it for this use case. I will just close this ticket. I think I can do that since I created it. *** This bug has been marked as a duplicate of bug 397172 ***