When importing a PNG, adding layers, and then attempting to save WITH THE SAME NAME but as a .KRA file the programme automatically saves it back as a PNG and user loses all layers! * ONLY if the user changes the file name does Krita THEN save as a .KRA file * Reproducible: Always Steps to Reproduce: 1. Open PNG file in Krita 2. Add paint layers 3. Hit "Save As" but do not change the file name. 4. The PNG saving box opens up and unwary users hits save thus saving as PNG and losing all layers 5. All attempts to save as Krita file are useless until the user changes the file name. Actual Results: As above Expected Results: Well one would expect that even if file name is not changed then choosing to save as .KRA file would work. I have saved screenshots if you wish to see.
Yes, this is default behaviour in other programs outside of Gimp though. And Gimp's system is kind of... hated.
You've got to be kidding me. I lost hours of work when I made the first save and thereafter just did a Ctrl-S not realising I was saving to PNG all the time. Luckily I was near the end of my work and didn't really need the layers anymore...
The behavior is intentional. There should be a (hideable) warning though.
Agreed, Sven, there absolutely should be some kind of user warning. When a user sees the .kra file extension and then hits save without paying a lot of attention there is the expectation that the file has been saved in Krita format.
You'd think that the PNG export options dialog would alert people... In any case, I don't think the issue can be solved by us. The problem is with the file dialog implementation. In order to get the native file dialog on Windows instead of the KDE or Qt one, we have to use the static methods of QFileDialog, and then we cannot get the value of the file type combobox: we should, but that is broken in Qt. And that means we also cannot figure out that the user is trying to save a bla.png as .kra (and what is it that they want, then? png or kra). On OSX, on the other hand, the system automatically detects the discrepancy and creates a bla.png.kra.
Thanks, Boudewijn, I fully appreciate that the PNG dialog box should alert people (i.e. me!) however, in lax moments (it's late, tired, not attentive, etc) verifying the Krita extension and then hitting save when the PNG dialog box pops up is an easy thing to do. In any event, I learned my lesson and if this is not an easy fix then so be it - I don't speak coder, so I'll take your word for it :)
This is just too big an issue to handle in the form of a bug report: designing a proper workflow for export/save-as is really difficult. Photoshop makes the default filetype psd, and save-as saves an png image you loaded as .png.psd... If you want to help to really fix this bug, you'd need to join the forum and start a thread that discusses the possible ways of working, and then possible implementations. We can't just change what Krita does right away....
Created attachment 97983 [details] attachment-13324-0.html Perfectly understandable. There are more important things to work on. Thanks. On Saturday, March 19, 2016 3:21 PM, Boudewijn Rempt via KDE Bugzilla <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=359104 Boudewijn Rempt <boud@valdyas.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |LATER Status|UNCONFIRMED |RESOLVED --- Comment #7 from Boudewijn Rempt <boud@valdyas.org> --- This is just too big an issue to handle in the form of a bug report: designing a proper workflow for export/save-as is really difficult. Photoshop makes the default filetype psd, and save-as saves an png image you loaded as .png.psd... If you want to help to really fix this bug, you'd need to join the forum and start a thread that discusses the possible ways of working, and then possible implementations. We can't just change what Krita does right away....