[krita] [Bug 479664] New: [Animation curves] "Add scalar keyframe" doesn't interpolate
https://bugs.kde.org/show_bug.cgi?id=479664 Bug ID: 479664 Summary: [Animation curves] "Add scalar keyframe" doesn't interpolate Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- STEPS TO REPRODUCE 1. Create a non-empty paint layer, add a transform mask to it. 2. Add 2 keyframes to the mask in the animation curves docker such that there's at least 1 frame between the two. 3. Select the frame (time) between the two keyframes and press the button "Add keyframe to control scalar property" OBSERVED RESULT The values of the keyframe added in step 3 copy the ones of the preceding frame. EXPECTED RESULT The values of the keyframe are linearly interpolated between the values of the surrounding keyframes. Note: the result is as expected if at step 3, instead of pressing the button, we create the keyframe via the transform tool. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION git-b034513065 (today's nightly) regression compared to 5.2.2 This was present at least as early as 5ffd6bebd0 (and so, unrelated to today's and yesterday's patches for animation curves) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478444] Transform mask updates incorrectly when editing tweens sequentially
https://bugs.kde.org/show_bug.cgi?id=478444 paleh changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from paleh --- Hi, Dmitry! Yes, the patch fixes the bug. I also checked another animation curve bug(s) that I reported (bug 478448 / bug 478452), but this wasn't fixing it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478735] New: "Convert shapes to vector selection" ignores transform and coordinate change
https://bugs.kde.org/show_bug.cgi?id=478735 Bug ID: 478735 Summary: "Convert shapes to vector selection" ignores transform and coordinate change Classification: Applications Product: krita Version: 5.2.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY Doing "Convert shapes to vector selection" on a vector object makes the selection appear at the position where the object was defined rather than where the object is located currently. STEPS TO REPRODUCE 1. Create a vector object on a vector layer Either: 2.a. Apply any transform (including moving) on the object using the transform tool or 2.b. Change the object's position relative to the origin of the canvas by rescaling or mirroring the canvas 3. Select the object with the Select shapes tool 4. Do Select->Convert shapes to vector selection OBSERVED RESULT The selection appears where the object was created. EXPECTED RESULT The selection appears around the object. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION Saving and reopening the document and doing steps 3-4 makes the selection appear at the expected position. This was present in 5.1.5 and is present on master (git-1fc417ae3e) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478521] New: RGB/HSX options disappear from the Specific color selector when switching to a layer in non-RGB space
https://bugs.kde.org/show_bug.cgi?id=478521 Bug ID: 478521 Summary: RGB/HSX options disappear from the Specific color selector when switching to a layer in non-RGB space Classification: Applications Product: krita Version: 5.2.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- STEPS TO REPRODUCE 1. Create a document in RGBA space. 2. Open the Specific color selector docker. It should be in RGBA space. 3. Create a layer in Grayscale space (e.g. a transparency mask). Select this layer in the layers docker. 4. In the specific color selector switch the mode between RGB and HSX OBSERVED RESULT The RGB/HSX options disappear. Switching to layers in RGBA doesn't bring them back. However, changing the space of the specific color selector to something else and back to RGBA does. EXPECTED RESULT RGB/HSX options don't disappear as long as the color selector is in RGBA space. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION This was present in 5.1.5 and is present on master (git-1fc417ae3e) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478520] New: Inconsistent undo may lead to data loss when creating a layer above global selection mask
https://bugs.kde.org/show_bug.cgi?id=478520 Bug ID: 478520 Summary: Inconsistent undo may lead to data loss when creating a layer above global selection mask Classification: Applications Product: krita Version: 5.2.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- STEPS TO REPRODUCE 0. "Show global selection mask" must be active. 1. Create a selection. 2. Create a new layer above the global selection mask (this happens naturally when the user calls "New Layer from Visible" for example) 3. Draw some strokes on this new layer. 4. Press Undo enough times to get to before step 1 (before the selection existed) 5. Press Redo. OBSERVED RESULT Pressing Redo any further doesn't bring back the layer created in step 2. Thus, all work done on that layer in steps 2-3 is lost. EXPECTED RESULT It is possible to redo all the way to the last action done in step 3. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION This was present in 5.1.5 and is present on master (git-1fc417ae3e) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478519] New: Inconsistent undo when converting global selection mask to transparency
https://bugs.kde.org/show_bug.cgi?id=478519 Bug ID: 478519 Summary: Inconsistent undo when converting global selection mask to transparency Classification: Applications Product: krita Version: 5.2.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- STEPS TO REPRODUCE 0. "Show global selection mask" must be active. 1. Create a selection. 2. Right click on the global selection mask in the layers docker and choose "Convert to transparency mask". 3. Press Undo twice (to get to before step 1). 4. Press Redo twice. OBSERVED RESULT After step 2, the selection mask doesn't exist. After step 4, it does. EXPECTED RESULT The state of the layers after step 2 is identical to that after state 4. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION I didn't find a way to create any actually serious problems which would be caused by this behavior, it's just inconsistent. This was present in 5.1.5 and is present on master (git-1fc417ae3e) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478452] New: [Animation curves] Canvas not updated when creating a frame in the beginning
https://bugs.kde.org/show_bug.cgi?id=478452 Bug ID: 478452 Summary: [Animation curves] Canvas not updated when creating a frame in the beginning Classification: Applications Product: krita Version: 5.2.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY When adding a frame in the animation curves docker before the first existing frame, the parameters of the new frame are set to default values (1 and 0 for scale and everything else respectively), but the canvas doesn't reflect that until the user switches to another frame and back. NB: not to be confused with bug 478448, which has the exact same steps to reproduce but is a different bug on master. STEPS TO REPRODUCE 1. Create a non-empty paint layer, add a transform mask to it. Select the mask. 2. In the animation curves docker add a frame to it at t = A, A >= 1. 3. Using the transform tool, make a change to the mask at A, e.g. a rotation. 4. Add a frame at t = B, B < A. OBSERVED RESULT At B the layer appears to have the same transformation as at A. Switching to another frame (time) and back to B makes it correctly appear as having the the empty (identity) transform. EXPECTED RESULT Creating the frame at B makes it immediately appear as it would without the transform mask. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION This appeared in 5.2.0, regression compared to 5.1.5. Present in 5.2 as of krita-5.2.2-24c985bda8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478448] New: [Animation curves] Wrong position when creating a frame in the beginning
https://bugs.kde.org/show_bug.cgi?id=478448 Bug ID: 478448 Summary: [Animation curves] Wrong position when creating a frame in the beginning Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY When adding a frame in the animation curves docker before the first existing frame, the coordinate system of the transform mask changes. STEPS TO REPRODUCE 1. Create a non-empty paint layer, add a transform mask to it. Select the mask. 2. In the animation curves docker add a frame to it at t = A, A >= 1. 3. Using the transform tool, make a change to the mask at A, e.g. a rotation. 4. Add a frame at t = B, B < A. OBSERVED RESULT After adding the frame, the layer at B is now placed with its center in the upper left corner of the canvas. EXPECTED RESULT After adding the frame at B, the layer should be exactly as if the transform mask was not there. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION This is not present in 5.2, only on master git-1fc417ae3e (12/12/2023) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478444] New: Transform mask updates incorrectly when editing tweens sequentially
https://bugs.kde.org/show_bug.cgi?id=478444 Bug ID: 478444 Summary: Transform mask updates incorrectly when editing tweens sequentially Classification: Applications Product: krita Version: 5.2.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY When editing one keyframe with the transform tool, then switching to edit another existing one, the keyframe data of the latter is replaced by the former, while the data of the former is replaced by the keyframe which precedes it. STEPS TO REPRODUCE 1. Create a non-empty paint layer, add a transform mask to it and select the mask. 2. In the animation curves docker add a new frame at some t = A. 3. Add another frame at t = B, B > A. 4. Using the transform tool, make a change at B, for example a translation. Press Enter. 5. Add another frame at t = C, C > B. 6. Using the transform tool, make a change at C. Press Enter. 7. Switch to A. 8. Select the transform tool. Click on the canvas. OBSERVED RESULT Keyframe data at A is replaced by the data at C. The data at C is replaced by the data at B. EXPECTED RESULT The data at A and C stays intact when the user initiates the transformation. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION Appeared in 5.2.0, regression compared to 5.1.5 In my opinion this is a severe bug because it makes tween animation borderline impossible (the best workaround I could find is to force the transform mask to apply to its current frame by making a change to the document (such as toggling the visibility of another layer) between editing each two existing frames -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478226] New: New layer from visible copies the red tint of the selection mask
https://bugs.kde.org/show_bug.cgi?id=478226 Bug ID: 478226 Summary: New layer from visible copies the red tint of the selection mask Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY Title STEPS TO REPRODUCE 1. Activate "Show global selection mask" 2. Make a selection which smaller than the size of the canvas 3. Switch to the selection mask in the layers docker. The canvas gets tinted red to indicate the non-selected area 4. Call "New layer from visible" OBSERVED RESULT The new layer "Visible" is tinted red. EXPECTED RESULT "Visible" is not tinted, because that tint is only a visualization tool SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION present in git-5ffd6bebd0, as well as 5.2.2 was already present in 5.1.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478225] New: Crash when undoing "New layer from visible" if it's animated
https://bugs.kde.org/show_bug.cgi?id=478225 Bug ID: 478225 Summary: Crash when undoing "New layer from visible" if it's animated Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create a new document 2. Create a frame on a paint layer (P) 3. Call "New layer from visible". A new layer "Visible" appears 4. Turn off the visibility of Visible 5. Select P in the layers docker 6. Press Undo twice OBSERVED RESULT Crash after second undo. Additionally, If layer P has onion skins active before step 3, creating a new layer from visible turns it off. EXPECTED RESULT Document returns to the state before step 3. Additionally, calling "new layer from visible" doesn't deactivate the onion skins. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION present in git-5ffd6bebd0, as well as 5.2.2 was already present in 5.1.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478009] New: Ratio doesn't affect the preview outline
https://bugs.kde.org/show_bug.cgi?id=478009 Bug ID: 478009 Summary: Ratio doesn't affect the preview outline Classification: Applications Product: krita Version: 5.2.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY I'm referring to the dynamic parameter which can be checked in the brush editor, not the static ratio of "Auto" brush tips. The preview outline of the brush is affected by other dynamic parameters, such as Size or Rotation, but not Ratio. STEPS TO REPRODUCE 1. Set "Brush outline shape" to "Preview outline". 2. Take a brush with the active "Ratio" parameter set to an easy-to-use sensor. 3. Draw with this brush while varying the input for the sensor. OBSERVED RESULT Brush dabs are affected by "Ratio", but the outline preview isn't. EXPECTED RESULT The outline is identical to the dabs that the brush will make. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477164] New: Preview outline of the brush tip is using opaque pixels to center
https://bugs.kde.org/show_bug.cgi?id=477164 Bug ID: 477164 Summary: Preview outline of the brush tip is using opaque pixels to center Classification: Applications Product: krita Version: 5.2.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- Created attachment 163253 --> https://bugs.kde.org/attachment.cgi?id=163253=edit Example of a brush tip and drawing a straight line with it STEPS TO REPRODUCE 1. Create a brush tip such that the center of the bounding box containing all its opaque pixels is clearly different from the geometric center of the brush tip's image. Use this brush tip on a simple brush such as Basic-2 Opacity. 2. Activate preview outline in general->cursor->brush outline shape (3. Activate any cursor in general->cursor->brush cursor icon for better visibility.) 4. Make the brush sufficiently big to see the details of the outline and draw. OBSERVED RESULT The preview of the brush tip is drawn around the center of the set of opaque pixels of the brush tip. Meanwhile, as we draw, individual dabs are (correctly) placed around the center of the full brush tip's image. Thus the preview outline is inconsistent with the dabs. EXPECTED RESULT The preview outline should be centered around the center of the full brush tip's image. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476924] New: Brush editor: errors when toggling "Share curves across all settings"
https://bugs.kde.org/show_bug.cgi?id=476924 Bug ID: 476924 Summary: Brush editor: errors when toggling "Share curves across all settings" Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- Created attachment 163107 --> https://bugs.kde.org/attachment.cgi?id=163107=edit video recording of the bug STEPS TO REPRODUCE 1. Open the brush editor (e.g. for Basic-5 Size) 2. Select an active parameter (e.g. Size) 3. Select an active sensor (e.g. Pressure) and modify its curve. 4. Uncheck "Share curves across all settings" 5. Observe the curves for all the other sensors of that parameter. OBSERVED RESULT Step 4 makes the curve for the selected sensor revert to its initial state, which is different from the behavior of "share curve across all settings" in 5.1.5. In step 5 we can see that the curves for some other sensors have unexpected shapes that we never defined. The set of affected sensors across different tries seems to be non-deterministic. Re-activating "Share..." on an affected sensor creates a new unexpected curve for that sensor and, contrary to the purported function of that checkbox, doesn't affect some other curves. EXPECTED RESULT Toggling "Share..." on sensor X should not change the curve for sensor X. Activating "Share..." on sensor X should set all the other sensors' curves to that of sensor X. Deactivating "Share..." on sensor X should not affect any of the curves. The behavior in 5.1.5 is keeping the curves for all the active sensors intact, while replacing the curves for the inactive sensors by the default "f(x)=x". SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION krita-5.3.0 (git d8e226389d) appeared in 5.2.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476715] New: Brush editor window: scaling issue when brush tip name is too long
https://bugs.kde.org/show_bug.cgi?id=476715 Bug ID: 476715 Summary: Brush editor window: scaling issue when brush tip name is too long Classification: Applications Product: krita Version: 5.2.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- Created attachment 162952 --> https://bugs.kde.org/attachment.cgi?id=162952=edit video demonstration SUMMARY Brush tips with long names (for example those generated as stamps) force elements the brush editor window to scale to an unusable dimension. The user have to manually rescale the window, which takes time and worsens the quality of life. STEPS TO REPRODUCE (0. It's probably better to to set up a fresh resource folder) 1. Open the brush editor for a pixel engine brush 2. Go to Brush tip->Predefined 3. Click on "Stamp". Leave the name field empty. 4. Click on "Save New Brush Preset". OBSERVED RESULT After step 3 the newly generated brush tip name showed in the right side of the screen is abbreviated as "" (although, as evident from the video, it is a little bit too long, forcing the list of brush tips on the left to rescale). After step 4 it is no longer abbreviated, making the element of the UI containing it to scale to unusable dimensions. EXPECTED RESULT The width of the cell with brush tip information should not depend on the length of the name. The displayed name should be always abbreviated to fit inside this cell. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Wayland Qt Version: 5.15.7 Appimage single screen 1920x1080 ADDITIONAL INFORMATION It was present in 5.1.5 but wasn't that much of a problem, because the full window would rescale. Present on master (krita-5.3.0-prealpha-e6ff66812a) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476511] Inconsistent undo and redo after flattening a layer
https://bugs.kde.org/show_bug.cgi?id=476511 --- Comment #5 from paleh --- Created attachment 162846 --> https://bugs.kde.org/attachment.cgi?id=162846=edit screen recording of the bug on 5.2.1-f819e29 No, nothing changed with the stable windows build #2035. I recorded a video to demonstrate it. Since it was only a Windows build that you restarted, and because I don't currently have a windows VM, I tested it in Wine, but the result is the same is the same for the stable appimage build #2040. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476514] New: Flattening a layer detaches its clones
https://bugs.kde.org/show_bug.cgi?id=476514 Bug ID: 476514 Summary: Flattening a layer detaches its clones Classification: Applications Product: krita Version: 5.2.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY Flattening a layer with masks or merging a group unlinks the clones of this layer. This is different from bug 351577 as here we're not talking about merging together two layers, one of which has a clone, but about flattening a container, which doesn't change the projection and thus doesn't require any update of the clone other than changing its source. Strictly speaking, this could be a feature request, but I find the absence of this unreasonable enough to be considered a bug. STEPS TO REPRODUCE 1. Create a paint or a group layer. 2. Create a clone of this layer. 3. Flatten or merge the original layer. OBSERVED RESULT The clone is no longer linked to anything, regardless of whether the original layer had any children. EXPECTED RESULT The clone is linked to the layer that results from flattening/merging. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476511] Inconsistent undo and redo after flattening a layer
https://bugs.kde.org/show_bug.cgi?id=476511 --- Comment #2 from paleh --- Hi, Dmitry Err, which build is it? I can reproduce the bug on 5.2.1-8a2e4c8b0e which you pushed today (at 12:01pm CET) in response to my other bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476512] New: Impossible to access undo history after making the background layer animated
https://bugs.kde.org/show_bug.cgi?id=476512 Bug ID: 476512 Summary: Impossible to access undo history after making the background layer animated Classification: Applications Product: krita Version: 5.2.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY Creation of the first frame on a layer is not undoable. For a 1-layer document it also means impossibility of accessing the undo history before the frame was created. STEPS TO REPRODUCE 1. Create a document with a single layer. 2. Draw several strokes on it. 3. Add a blank keyframe to it. 4. Press undo several times. OBSERVED RESULT All the strokes done in step 2 remain throughout the undoing. EXPECTED RESULT Undos allow to access all the intermediate states of the layer's history. Optionally, pressing undo once in step 4 (undoing the creation of the frame) should return the layer to a non-animated state SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476511] New: Inconsistent undo and redo after flattening a layer
https://bugs.kde.org/show_bug.cgi?id=476511 Bug ID: 476511 Summary: Inconsistent undo and redo after flattening a layer Classification: Applications Product: krita Version: 5.2.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY Canvas isn't properly updated when undoing and redoing a flattening of a layer. STEPS TO REPRODUCE 1. Add a new frame on a paint layer 2. Draw something on it 3. Add a mask (filter, transparency,...) to this layer. 4. Flatten the animated layer. 5. Press undo 6. Press redo OBSERVED RESULT The layer disappears. Repeating steps 5-6 brings it back. EXPECTED RESULT After step 6 the canvas returns to its state after step 4. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION It's probably related to bug 474122. I'm creating this ticket because there it's phrased as a "warning", whereas here this is a concrete error. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476495] Incorrect flattening of animated layers with filter masks
https://bugs.kde.org/show_bug.cgi?id=476495 --- Comment #6 from paleh --- I tried the linux build and couldn't find anything wrong. While trying to break it, I did discover a couple of other animation bugs , but they weren't caused by neither this commit nor the introduction of the new merging method. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476472] Merging a non-animated layer into an animated one only works for the first two frames
https://bugs.kde.org/show_bug.cgi?id=476472 --- Comment #5 from paleh --- Created attachment 162839 --> https://bugs.kde.org/attachment.cgi?id=162839=edit video recording of the bug Here's the screen capture of me reproducing the bug. I've noticed two more things: - there's some non-determinism involved - sometimes the merger happens correctly, and sometimes it happens on an incorrect frame (once the non-animated layer got merged into frame 2 when I was merging it on frame 3, but I couldn't reproduce that). The most common scenario is the one I'm showing here, when the top layer disappears. - I couldn't reproduce the bug on the windows version with wine -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476472] Merging a non-animated layer into an animated one only works for the first two frames
https://bugs.kde.org/show_bug.cgi?id=476472 --- Comment #4 from paleh --- Sorry, disregard my previous comment, it does also happen on 5.3. It's just that there's some order of selecting frames when the merging happens as expected (into the current frame), but I can't figure out what it is. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476472] Merging a non-animated layer into an animated one only works for the first two frames
https://bugs.kde.org/show_bug.cgi?id=476472 --- Comment #3 from paleh --- Oh, I should add that the bug is present in 5.2.1 (release version on krita.org) but not on master (5.3.0-7258fce19ce). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476472] Merging a non-animated layer into an animated one only works for the first two frames
https://bugs.kde.org/show_bug.cgi?id=476472 --- Comment #2 from paleh --- Hi, Dmitry, I've reported the bug precisely after going through the commits to see what's new in 5.2.1 and trying it out for myself. Have you tried reproducing the bug and were unable to? I do confirm that, when merged on frame >= 3, the non-animated layer's pixels disappear (on all the frames) instead of getting merged into the animated one, as I stated in the report. But maybe I'm misunderstanding and you're asking for something else? Or maybe I wasn't clear in the report? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476495] New: Incorrect flattening of animated layers with filter masks
https://bugs.kde.org/show_bug.cgi?id=476495 Bug ID: 476495 Summary: Incorrect flattening of animated layers with filter masks Classification: Applications Product: krita Version: 5.2.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- Created attachment 162833 --> https://bugs.kde.org/attachment.cgi?id=162833=edit frame 3 after flattening on frame 1 STEPS TO REPRODUCE 1. Create an empty paint layer. 2. Create several (at least 3) frames on this layer. Draw something on these frames such that the bounding boxes of the frames intersect but don't entirely cover each other. 3. Add a filter mask for this layer, for example HSV/HSL Adjustment. 4. Switch to the first frame. 5. Flatten the animated layer. OBSERVED RESULT Switching to other frames, we can see that they contain elements of other frames. In the attached screenshot, each frame originally contained only one number, but after flattening frame 3 now contains parts of all 3 of them. EXPECTED RESULT Flattening keeps all the frames consistent with their projection before flattening. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION Bug is present in 5.2.0 and 5.3.0-7258fce19ce but is not present in 5.1.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476472] New: Merging a non-animated layer into an animated one only works for the first two frames
https://bugs.kde.org/show_bug.cgi?id=476472 Bug ID: 476472 Summary: Merging a non-animated layer into an animated one only works for the first two frames Classification: Applications Product: krita Version: 5.2.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- STEPS TO REPRODUCE 1. Create a paint layer with 3 or more frames 2. Add a layer above, draw something on this layer 3. In the animation timeline docker select the third (or any further) frame 4. Merge down the layer created in step 2 into the animated one OBSERVED RESULT The contents of the non animated layer disappear. EXPECTED RESULT The non animated layer is merged into the frame selected in step 3. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475927] New: Colorize tool: missing canvas updates on Edit key strokes and Show coloring
https://bugs.kde.org/show_bug.cgi?id=475927 Bug ID: 475927 Summary: Colorize tool: missing canvas updates on Edit key strokes and Show coloring Classification: Applications Product: krita Version: 5.2.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Colorize Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- Formally , this is 2 different bugs, but since they may be related I decided to report them together. STEPS TO REPRODUCE 1. Select the Colorize tool. Click on a paint layer to add a colorize mask. 2. Draw a stroke on the mask 3. In the tool options, click on update, wait for it to finish. 4. Uncheck "Edit key strokes" 5. Check "Edit key strokes" back <- error #1 6. Toggle "Show coloring" twice (in the layers docker) 7. Uncheck "Edit key strokes" 8. Uncheck "Show coloring" 9. Check "Show coloring" <- error #2 OBSERVED RESULT Step 5 has no immediate effect. Toggling "Show coloring" twice makes the canvas re-enter the strokes editing mode. Step 9 has no immediate effect. Toggling "Edit key strokes twice" makes the coloring reappear. EXPECTED RESULT Step 5 makes the canvas enter the stroke editing mode immediately. Step 9 makes the coloring appear immediately. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION The bug was not present in 5.1.5. It appeared at some point between 5.2.0-prealpha git 6c2a270 (30/11/2022) and 5.2.0-beta1 (27/06/2023) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475860] New: Quick-ungrouping a group with a mask may lead to data loss
https://bugs.kde.org/show_bug.cgi?id=475860 Bug ID: 475860 Summary: Quick-ungrouping a group with a mask may lead to data loss Classification: Applications Product: krita Version: 5.2.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY When ungrouping a group containing any mask (except a selection mask) the layers located below the mask are correctly ungrouped, whereas the mask and the all layers above are deleted. Undoing this operation doesn't bring the mask back, leading to a potential data loss. STEPS TO REPRODUCE 1. Create a group with at least one layer 2. Create a mask (e.g. a transparency mask) inside the group, and place it below a layer. The mask should be applied to the group itself, not the layer. 3. Execute some operations on the mask (e.g. draw some strokes if it's a transparency) 4. Right click the group layer and do Group->Quick Ungroup 5. Press undo. 6. Press undo. OBSERVED RESULT After step 4, the layers above the mask have disappeared. After step 5, the group is back, but it no longer contains the mask. After step 6, which should undo the last operation done in step 3, nothing happens, as there is no mask to apply the change to. If the user can undo until step 1, then pressing "redo" enough times will bring the mask and all the work back. However if the undo stack has been exceeded, all the work done in step 3 will be lost. EXPECTED RESULT When ungrouping, layers above the mask should not get lost. Masks should be at least recoverable through undo and, ideally, available after the ungrouping. For example filter and transparency mask could get converted to filter and transparency layers (maybe this should happen whenever a mask is created/dragged inside a group layer?). Alternatively, ungrouping could just push the regular layers outside the group while keeping the group layer as the container for the masks, if they are present. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 ADDITIONAL INFORMATION also present in 5.1.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466840] Using the Move tool or the Transform tool on a cloned frame unlinks it from its source
https://bugs.kde.org/show_bug.cgi?id=466840 --- Comment #2 from paleh --- No, it doesn't happen in 5.2. Bug 466843 can be removed as well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467861] New: Copying a selection from a layer with alpha inheritance offsets the copy
https://bugs.kde.org/show_bug.cgi?id=467861 Bug ID: 467861 Summary: Copying a selection from a layer with alpha inheritance offsets the copy Classification: Applications Product: krita Version: 5.1.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create an empty paint layer 2. Draw something on it (for better visibility draw in the upper left quarter of the canvas) 3. Set the layer's alpha inheritance on 4. Switch to any selection tool. Make a selection around the drawing. 5. Right click on the canvas and choose "Copy Selection to New Layer" OBSERVED RESULT The copied selection is offset relative to the original. The offset appears to be half of the canvas's resolution in each dimension. EXPECTED RESULT The copied selection is copied at the position of the original. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.12.12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466902] Cloning undefined frames results in a crash
https://bugs.kde.org/show_bug.cgi?id=466902 --- Comment #1 from paleh --- Created attachment 157020 --> https://bugs.kde.org/attachment.cgi?id=157020=edit long backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466902] New: Cloning undefined frames results in a crash
https://bugs.kde.org/show_bug.cgi?id=466902 Bug ID: 466902 Summary: Cloning undefined frames results in a crash Classification: Applications Product: krita Version: 5.1.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- Created attachment 157019 --> https://bugs.kde.org/attachment.cgi?id=157019=edit short backtrace SUMMARY Title. On windows it also results in an unexpected behavior, as well as a crash (see Additional Info). STEPS TO REPRODUCE 1. Create a new paint layer A. 2. Add a blank* frame on A. 3. By holding Shift or Ctrl select several undefined keyframe slots** in the timeline of A. 4. Right click and choose "Clone Keyframes". 5. Create a new paint layer B, add a blank frame to it. 6. Right click on B's timeline and choose "Paste Keyframes"*** * whether or not the frames are blank does not impact the result ** the selection needs to contain at least one undefined frame and one other frame (defined or undefined) *** cloning by Alt+dragging does not result in a crash OBSERVED RESULT - krita crashes EXPECTED RESULT - krita doesn't crash - pasting undefined cloned frames has no impact - pasting an array of mixed defined and undefined cloned frames duplicates the defined frames, while undefined frames make no impact. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.12.12 ADDITIONAL INFORMATION The issue exists on Windows in a different form. When an undefined frame is cloned (and pasted) on B, it is replaced by a duplicate of the next defined frame in the timeline of A (the expected result is that pasting undefined frames shouldn't affect the timeline of B). If no such frame exists, Krita crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466843] New: Undo works incorrectly in a certain case involving clone frames
https://bugs.kde.org/show_bug.cgi?id=466843 Bug ID: 466843 Summary: Undo works incorrectly in a certain case involving clone frames Classification: Applications Product: krita Version: 5.1.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY This exists because of https://bugs.kde.org/show_bug.cgi?id=466840 - using the Move tool on a cloned frame unlinks the clone from the original, and it isn't taken into account by the Undo function. STEPS TO REPRODUCE 1. Create an empty frame 2. Draw a single brushstroke on that frame 3. Clone (and paste) the frame (next 2 steps must be each a single step wrt the undo stack) 4. Draw another single stroke on the clone 5. Switch to the Move tool, move the picture and press Enter 6. Undo exactly 2 times (to the state before step 4) OBSERVED RESULT The original frame is in the state it was before step 4 - it contains a single brushstroke - whereas the clone frame (now unlinked from its source) incorrectly contains 2 strokes. EXPECTED RESULT Both frames must return to the state they were before step 4. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.12.12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466840] New: Using the Move tool or the Transform tool on a cloned frame unlinks it from its source
https://bugs.kde.org/show_bug.cgi?id=466840
Bug ID: 466840
Summary: Using the Move tool or the Transform tool on a cloned
frame unlinks it from its source
Classification: Applications
Product: krita
Version: 5.1.5
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Animation
Assignee: krita-bugs-n...@kde.org
Reporter: paleh21...@proton.me
Target Milestone: ---
SUMMARY
See title
STEPS TO REPRODUCE
1. Create an empty frame on a paint layer
2. Draw some pixels in this frame
3. Clone (and paste) the frame
4. Either:
- using the Transform tool, apply any transformation (e.g. rotation) on the
pixels on the frame and press Enter
- using the Move tool, move the pixels on the frame
('the frame' can be either the original or the cloned frame)
OBSERVED RESULT
The 2 frames stop being linked after step 4. Changes done to one (including the
initial transform/move) don't apply to the other.
EXPECTED RESULT
The 2 frames stay linked.
SOFTWARE/OS VERSIONS
Linux: Ubuntu 22.04
Qt Version: 5.12.12
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 463113] Pasting as reference when plain text is in the clipboard causes a crash
https://bugs.kde.org/show_bug.cgi?id=463113 --- Comment #2 from paleh --- This could potentially be related to https://bugs.kde.org/show_bug.cgi?id=463858 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463858] New: Pasting into a vector layer when plain text is in the clipboard causes a crash
https://bugs.kde.org/show_bug.cgi?id=463858 Bug ID: 463858 Summary: Pasting into a vector layer when plain text is in the clipboard causes a crash Classification: Applications Product: krita Version: 5.1.4 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Copy some plain text into the clipboard, e.g. "123" 2. Create a new vector layer 2. Paste by pressing Ctrl+V OBSERVED RESULT Krita crashes EXPECTED RESULT Pasting a non-image has no effect and Krita doesn't crash SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04.1 LTS Qt Version: 5.12.12 ADDITIONAL INFORMATION -The last line of the bug report is: ASSERT (krita): "!qimage.isNull()" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/kis_clipboard.cc, line 460 - Maybe this bug is related to https://bugs.kde.org/show_bug.cgi?id=463113 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463230] Canvas isn't updated correctly in a certain scenario of using the colorize mask
https://bugs.kde.org/show_bug.cgi?id=463230 --- Comment #2 from paleh --- Created attachment 154692 --> https://bugs.kde.org/attachment.cgi?id=154692=edit Step 5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463230] Canvas isn't updated correctly in a certain scenario of using the colorize mask
https://bugs.kde.org/show_bug.cgi?id=463230 --- Comment #1 from paleh --- Created attachment 154691 --> https://bugs.kde.org/attachment.cgi?id=154691=edit Step 3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463230] New: Canvas isn't updated correctly in a certain scenario of using the colorize mask
https://bugs.kde.org/show_bug.cgi?id=463230 Bug ID: 463230 Summary: Canvas isn't updated correctly in a certain scenario of using the colorize mask Classification: Applications Product: krita Version: 5.1.4 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Colorize Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- Created attachment 154690 --> https://bugs.kde.org/attachment.cgi?id=154690=edit Result SUMMARY Checking "Limit to layer bounds" after the colorize mask had already been created for the entire canvas doesn't reinitialize the area outside the bounds STEPS TO REPRODUCE 1. Create new layer 2. Draw something on this layer, but such that its allocated size remains strictly inferior to the size of the canvas 3. Switch to Colorize Mask Tool, create a colorize mask for this layer, add some strokes to the mask 4. In Tool Options, while "Limit to layer bounds" is unchecked, click on "Update" and wait for the operation to finish 5. Check "Limit to layer bounds" 6. Click on "Update" again and wait for the operation to finish OBSERVED RESULT As evident from the screenshot, the canvas is updated incorrectly outside of the area of the smallest rectangle containing both the layer's and the mask's strokes. Zooming, panning or turning off the visibility for the colorize mask doesn't update it either. EXPECTED RESULT The outside area should be blank SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04.1 LTS Qt Version: 5.12.12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463113] New: Pasting as reference when plain text is in the clipboard causes a crash
https://bugs.kde.org/show_bug.cgi?id=463113 Bug ID: 463113 Summary: Pasting as reference when plain text is in the clipboard causes a crash Classification: Applications Product: krita Version: 5.1.4 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Copy some plain text into the clipboard, e.g. "123" 2. In Krita switch to reference tool, right click and paste (or press Ctrl+Shift+R) OBSERVED RESULT Krita crashes EXPECTED RESULT Pasting a non-image has no effect and Krita doesn't crash SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04.1 LTS Qt Version: 5.12.12 ADDITIONAL INFORMATION -The issue exists in 5.1.3 as well -I discovered it when I was working with selections holding my fingers ready to click Ctrl+Shift+A (deselect) and Ctrl+R (rect. selection tool) and accidentally pressed Ctrl+Shift+R, so, despite the nonsensical nature of pasting text as reference, other users are somewhat likely to encounter this crash too -The last line of the bug report is: ASSERT (krita): "!qimage.isNull()" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/kis_clipboard.cc, line 460 -- You are receiving this mail because: You are watching all bug changes.
