https://bugs.kde.org/show_bug.cgi?id=517102
Bug ID: 517102
Summary: Translucent layer makes other document tabs visible on
canvas
Classification: Applications
Product: krita
Version First 6.0.0-beta2
Reported In:
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: minor
Priority: NOR
Component: OpenGL Canvas
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 190358
--> https://bugs.kde.org/attachment.cgi?id=190358&action=edit
Screenshot showing a layer with three black question marks at 64% opacity, with
the other document (a chibi drawing) visible.
SUMMARY
When multiple documents are open in Krita, and the current document contains a
layer at low opacity with no solid pixels to fill the canvas behind it, the
other document is visible.
STEPS TO REPRODUCE
1. Set Krita's Multiple Document Mode to Tabs in Configure Krita > General >
Window.
2. Create or open a document. You can leave it empty, but some distinctive
content would make the problem easier to see.
3. Create a new document with a transparent background, i.e. background opacity
set to 0 in the Content tab (it's possible deleting the background layer works
too, but I no longer have 6.0.0 installed to check)
4. Create a second layer, and draw or paste something in it, ideally with a
large-ish solid shape. I initially noticed it while working with photos, but
brush strokes "work" too.
5. Set that layer's opacity to below 100%. Around 50% should make the problem
clearly visible.
OBSERVED RESULT
The other document tab is visible in the translucent portions of the layer. You
may need to zoom in and/or pan around the image so that the translucent pixels
overlap recognizable parts of the other tab, such as a distinctive element or
the image border.
EXPECTED RESULT
The other document should not be visible, the translucent portions of the layer
should blend only with the transparency checkerboard.
SOFTWARE/OS VERSIONS
Windows: 10
Qt Version: 6.x
ADDITIONAL INFORMATION
I was not able to reproduce this in 5.3.0-beta2, so this is likely a Qt6 issue.
I tested with graphics acceleration enabled, renderr: Direct3D via ANGLE. I did
not think to try other rendering options before installing 5.3.0-beta2, oops.
--
You are receiving this mail because:
You are watching all bug changes.
