Created attachment 113456 [details] Screenshot of the error message pls link to this bugreport at RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1593227 Description of problem: The message highlited states: That I will loose informations when i safe the image, as it will get flatten. but, the PNG image never had any layers. The error message is an error in itself :) Version-Release number of selected component (if applicable): 4.0.3
Hi, When you open a PNG under Krita, during the time of the edition your picture's pixels have the potential to get multilayered and also all the features of Krita(Assistants, Grids, Rulers). Krita 4.0.3 (tested on appimage) doesn't trigger the warning if you just open a PNG, edit painting on it, and save it. The message appears when special features were in use during the time of editing (eg. adding an assistant). Please describe a step-by-step procedure to reproduce the scenario on a file where you estimate the warning message is an error.
Version A 1. Taking a Screenshot via Cinnamonds Screensshottool 2. open krita for editing from the picture preview in nemo 3. Trimming the picture to a smaller area 4. Hitting CTRL+S 5. getting this message. B 2. open krita for editing from the picture preview in nemo for any picture 3. Trimming the picture to a smaller area 4. Hitting CTRL+S 5. getting this message.
Created attachment 113458 [details] RAW unaltered Image for testing
Thank you for the informations. The behavior you describe sounds totally normal: by having a selection (I can see the marching ants on your screenshot) you add informations on the canvas that Krita will not able to save in a PNG image. The warning message here does perfectly its job and act on purpose. Can you reproduce if you go to Select > Deselect Before saving?
Confirmed: "Deselecting All" before calling the save dialog avoids the message.
Ok. So, the only thing to fix here is the error message. It needs to list more reasons than just multi-layers. From: > You will lose information when saving this image as a PNG image. Reason: > - The image has more than one layer. Only the flattened image will be saved. To: > You will lose information when saving this image as a PNG image. POSSIBLE reasonS: > - The image has more than one layer. Only the flattened image will be saved. > - The image contains a selection. This data will be lost > - The image contains (Assistants, Grids, Rulers). This data will be lost.
Git commit bec019d1fd4e4d2fc7d07856b202dc03665b9504 by Boudewijn Rempt. Committed on 20/06/2018 at 12:05. Pushed by rempt into branch 'master'. Improve the message in the multilayer check M +1 -1 libs/impex/MultiLayerCheck.h https://commits.kde.org/krita/bec019d1fd4e4d2fc7d07856b202dc03665b9504
Git commit 9eb1c15eb90b7777558cd6c1982eda7d2ef2060b by Boudewijn Rempt. Committed on 20/06/2018 at 12:05. Pushed by rempt into branch 'krita/4.1'. Improve the message in the multilayer check (cherry picked from commit 3017c443022ef564d298fa53cb29d20bfc0cfe5f) M +1 -1 libs/impex/MultiLayerCheck.h https://commits.kde.org/krita/9eb1c15eb90b7777558cd6c1982eda7d2ef2060b
Aw, I pushed an improved message before I saw your suggestion...
assistants shouldn't trigger the issue, though. Maybe reference images would.
ähmmmm... "improoving the message" isn't the correct behaviour. Add a check if the selected area is the only reason for the message and than supressing it would be the right way to solve this. Your Approach is "This is an error message for an error thats not an error at all." Sorry, not acceptable :D
@BlenderIRC: It is not an error message; it is a warning and the saving pop-up is not designed to be a validator with checkbox. So, the commit and solution looks acceptable to me and good enough to informs the user about what is happening. You can mark the bug solved on bugzilla.redhat.com. @Boud: Thank you for the super quick fix @Boud!
Sorry, i have to insist, that adding more informations to a message, that should never be triggered in the first place, isn't a solution at all. Any userinteraction should be as easy & clear as possible. This error message should simply not there for what happened. Even a fix like "we autotrigger deselect() before opening a savecontext" would be better than this! If you just add an additional line of infos, noone will read this, as all you can see directly without clicking on the error message, is not helpful at all and does not change due to your solution. So it's not only "not a solution", but also "not helpful at all" :D Accept it, keeping that message there, for an open areaselecting, is just wrong. If you don't trust me, give it to the QA contact, he/she will see this in the same way.
What QA contact?
Quality Assurance -> Team Leadership -> Main Designer -> Master of Deaster -> Someone who does the UI decisions that kind of contacts ;)
Yes, I know what QA means. I think you might be under a misapprehension here. This is an open source project, not a company. We've got a full-time project maintainer and lead developer (me, funded by sales in the Windows Store), another full-time developer (funded by donations) and a bunch of volunteers from all over the world. We make decisions together, and we have a volunteer who does a lot of UI polish work, but we do not have a "QA contact".
Your right, from the job done so far, i was imagening a bigger team for krita, as it's one of the lighthouse projects for OSS development. Ok, in this case, take it from a guy whos coding for 35 years now: Adding this hint messages does not help the user whos seeing the dropbox, because hes not clicking there, as i did. Users don't tend to do this, it's not obvious for the work flow. The better way is to add a check before the message is displayed, who ensures, that it's only shown when really needed. Displaying the selection area will never be noticed as a "mistake/bug/reason" for displaying this error message. I already talked with different people about this matter today, and they all agree, that what you planed, does not solve the problem. I doN#t argument for myself, as i now know what and why it happens, but normal users with no background will never understand why you display a message, and write inside, that he can ignore it, when ... Normal users will always consider it as a major bug when a warning message is shown. There is no way to deny this. Go grab your neigbour , place him infront of your terminal, let him execute the steps, and check his reaction to the message box. You will instantly accept all I tried to tell you today ;) You will see.. trust an old dev ;)
Git commit c7fb30c297d4c36360500b2cd8a65038a8db8688 by Andrey Kamakin, on behalf of Boudewijn Rempt. Committed on 26/06/2018 at 14:18. Pushed by akamakin into branch 'akamakin/T8628-multithreading-optimization'. Improve the message in the multilayer check M +1 -1 libs/impex/MultiLayerCheck.h https://commits.kde.org/krita/c7fb30c297d4c36360500b2cd8a65038a8db8688