Bug 427317

Summary: Fill layers: Malformed preview rendering when switching to and quickly switching from Multigrid option
Product: [Applications] krita Reporter: tomtomtomreportingin
Component: GeneralAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: halla, lynx.mw+kde
Priority: NOR    
Version: 4.4.0-beta2   
Target Milestone: ---   
Platform: Appimage   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Malformed preview after performing the steps

Description tomtomtomreportingin 2020-10-04 09:06:39 UTC 
SUMMARY
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.

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

OBSERVED RESULT
The rendering preview is malformed. See attachment.

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

SOFTWARE/OS VERSIONS
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)

ADDITIONAL INFORMATION
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 ***