Bug 427317 - Fill layers: Malformed preview rendering when switching to and quickly switching from Multigrid option
Summary: Fill layers: Malformed preview rendering when switching to and quickly switch...
Status: RESOLVED DUPLICATE of bug 427199
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 4.4.0-beta2
Platform: Appimage Linux
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
: 427316 (view as bug list)
Depends on:
Reported: 2020-10-04 09:06 UTC by tomtomtomreportingin
Modified: 2020-10-04 09:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Malformed preview after performing the steps (358.58 KB, image/png)
2020-10-04 09:07 UTC, tomtomtomreportingin

Note You need to log in before you can comment on or make changes to this bug.
Description tomtomtomreportingin 2020-10-04 09:06:39 UTC
While creating a new Fill layer, if you switch to Multigrid and then quickly switch to another option like Pattern, you'll get a malformed preview showing both types.

1. Add Fill layer
2. Switch to Multigrid
3. Quickly after step 2, switch to another option.

The rendering preview is malformed. See attachment.

The option you switched to in step 3 should be correctly shown.

Linux/KDE Plasma: Debian sid
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.12.9 (Appimage)

This happens regardless if it's CPU canvas or OpenGL canvas.

This only happens when creating the fill layer, not when editing the properties of an already created fill layer.

I marked this as minor as the final render comes out fine regardless of how the preview looks.

If step 3 is not done immediately after step 2, the preview looks normal.
Comment 1 tomtomtomreportingin 2020-10-04 09:07:41 UTC
Created attachment 132107 [details]
Malformed preview after performing the steps
Comment 2 Halla Rempt 2020-10-04 09:10:11 UTC
*** Bug 427316 has been marked as a duplicate of this bug. ***
Comment 3 Lynx3d 2020-10-04 09:48:45 UTC
Isn't this the same issue as Bug 427199 ?
Comment 4 Halla Rempt 2020-10-04 09:59:51 UTC
Yes, I just couldn't find that report when I marked the accidental duplicate as a duplicate.

*** This bug has been marked as a duplicate of bug 427199 ***